You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 Re: Installation » Upgrading to Excalibur » 2025-08-19 10:04:15
Yes. I think that you should wait a little. Is the third day I try to restore the login part.
#2 Re: Installation » Upgrading to Excalibur » 2025-08-18 11:49:16
And when I thought that everything went smooth I encountered something very strange on 2 machines (one is host and another is guest of VirtualBox). On both after the upgrade lxdm just hangs. I can login using slim, but I am using cwm and all my starting stuff was in .xsession. I looked in the logs and I can't seem to find anything. Any idea?
#3 Re: Installation » Upgrading to Excalibur » 2025-08-18 11:46:55
I think you would do fine with the 237 partition. Moving to LVM is tricky.
#4 Re: Installation » Upgrading to Excalibur » 2025-08-14 06:03:39
Everything went so smooth! I think that only OpenBSD has the same easy upgrade process. Is my second release upgrade and I am not for a moment regretting the switch to Devuan some 3 years ago. It is the Linux distro I was waiting from 1999 (when I first started using Linux).
#5 Re: Installation » Upgrading to Excalibur » 2025-08-12 07:02:22
Thank you! I think I should start the upgrade now. But first a backup 
#6 Re: Installation » Upgrading to Excalibur » 2025-08-12 06:54:26
I also have 2 kernels
drwxr-xr-x 4 root 1.0K Aug 12 09:51 ./
drwxr-xr-x 22 root 4.0K Aug 11 13:21 ../
-rw-r--r-- 1 root 254K May 18 15:01 config-6.1.0-36-amd64
-rw-r--r-- 1 root 254K May 22 21:32 config-6.1.0-37-amd64
drwxr-xr-x 5 root 1.0K Aug 12 09:51 grub/
-rw-r--r-- 1 root 47M Jun 6 09:26 initrd.img-6.1.0-36-amd64
-rw-r--r-- 1 root 47M Jun 10 08:40 initrd.img-6.1.0-37-amd64
drwx------ 2 root 12K May 23 2024 lost+found/
-rw-r--r-- 1 root 83 May 18 15:01 System.map-6.1.0-36-amd64
-rw-r--r-- 1 root 83 May 22 21:32 System.map-6.1.0-37-amd64
-rw-r--r-- 1 root 7.9M May 18 15:01 vmlinuz-6.1.0-36-amd64
-rw-r--r-- 1 root 7.9M May 22 21:32 vmlinuz-6.1.0-37-amd64
and
/dev/sda1 455M 120M 310M 28% /boot
Do you think will be enough? Should I remove the 6.1.0-36 kernel also?
#7 Re: Installation » Upgrading to Excalibur » 2025-08-12 06:46:23
I looked on the link from above (https://www.debian.org/releases/trixie/ … ssues.html) and it has this section
5.1.5. Ensure /boot has enough free space
The Linux kernel and firmware packages have increased considerably in size in previous Debian releases and in trixie. As a result your /boot partition might be too small, causing the upgrade to fail. If your system was installed with Debian 10 (buster) or earlier, your system is very likely to be affected.
Before starting the upgrade, make sure your /boot partition is at least 768 MB in size, and has about 300 MB free. If your system does not have a separate /boot partition, there should be nothing to do.
If /boot is in LVM and too small, you can use lvextend to increase the size of an LVM partition. if /boot is a separate partition it is likely easier to reinstall the system.
#8 Re: Installation » Upgrading to Excalibur » 2025-08-12 06:09:08
Thank you for the links with the issues. I think there is one that could be really a trouble - my /boot partition has only 487M and is not in a logical volume. Should I try to resize it or in devuan will be enough?
#9 Re: Installation » Upgrading to Excalibur » 2025-08-11 11:48:05
Thank you! I'll give it a try.
#10 Installation » Upgrading to Excalibur » 2025-08-11 08:44:02
- samarul
- Replies: 17
Hello to you all!
Hope my message will not be considered as stupid. Now that Debian 13 is live is it safe to assume that upgrading to Excalibur means for Devuan the equivalent to upgrading to Debian 13?
Installing usrmerge and then doing a apt-get upgrade and apt-get dist-upgrade is enough for a smooth upgrade from Daedalus or should I pay attention to something else also?
Thank you!
#11 Re: Desktop and Multimedia » Thunar segmentation fault as user » 2023-06-15 11:29:24
I have no idea what it is. I deleted $HOME/.cache and $HOME/.config/Thunar and $HOME/.config/xfce4. Nothing changed.
As root, as I mentioned, there is no problem.
L.E.: I killed the X session, I removed again the mentioned folder, rebooted and then login again. Thunar started. Let's see if I can mark it as solved.
#12 Desktop and Multimedia » Thunar segmentation fault as user » 2023-06-15 07:21:03
- samarul
- Replies: 3
Hello to you all!
Everything went smooth for more than a year in Devuan Chimaera, but today Thunar just got crazy. I get
Segmentation faultas regular user, but I can use it as root.
Some information about the system and Thunar version
$ thunar --version
thunar 4.16.8 (Xfce 4.16)
$ uname -a
Linux dvn 5.10.0-23-amd64 #1 SMP Debian 5.10.179-1 (2023-05-12) x86_64 GNU/LinuxThis is some messages from
/var/log/messagesJun 15 10:00:55 dvn kernel: [ 2293.180833] thunar[26193]: segfault at 8c0000003a ip 00007f0e1ed2ff1c sp 00007ffd4e6b7030 error 4 in libglib-2.0.so.0.6600.8[7f0e1ecdc000+88000]
Jun 15 10:00:55 dvn kernel: [ 2293.180856] Code: ff eb dc 0f 1f 00 48 c1 e8 04 4c 8b 2b 8d 48 ff 48 89 c5 49 89 cf 49 c1 e7 04 4d 01 fd 4d 8b 65 00 4d 85 e4 0f 84 e4 00 00 00 <49> 8b 44 24 08 48 85 c0 74 4a 48 8b 10 49 89 54 24 08 49 89 c4 49
Jun 15 10:03:28 dvn kernel: [ 2446.587404] perf: interrupt took too long (5110 > 5095), lowering kernel.perf_event_max_sample_rate to 39000
Jun 15 10:10:28 dvn kernel: [ 2866.922234] perf: interrupt took too long (6389 > 6387), lowering kernel.perf_event_max_sample_rate to 31250
Jun 15 10:13:57 dvn kernel: [ 3075.231332] thunar[16154]: segfault at 8c0000003a ip 00007fb666309f1c sp 00007ffc984ccd90 error 4 in libglib-2.0.so.0.6600.8[7fb6662b6000+88000]
Jun 15 10:13:57 dvn kernel: [ 3075.231356] Code: ff eb dc 0f 1f 00 48 c1 e8 04 4c 8b 2b 8d 48 ff 48 89 c5 49 89 cf 49 c1 e7 04 4d 01 fd 4d 8b 65 00 4d 85 e4 0f 84 e4 00 00 00 <49> 8b 44 24 08 48 85 c0 74 4a 48 8b 10 49 89 54 24 08 49 89 c4 49And this is what I got from debugging
$ thunar -q
user@dvn:~
$ gdb
fGNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb) file /usr/bin/thunar
Reading symbols from /usr/bin/thunar...
(No debugging symbols found in /usr/bin/thunar)
(gdb) run
Starting program: /usr/bin/thunar
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff5ce2700 (LWP 32298)]
[New Thread 0x7ffff54e1700 (LWP 32299)]
[New Thread 0x7ffff497f700 (LWP 32311)]
[New Thread 0x7fffe7fff700 (LWP 32313)]
[Thread 0x7fffe7fff700 (LWP 32313) exited]
Thread 1 "thunar" received signal SIGSEGV, Segmentation fault.
0x00007ffff715ff1c in g_slice_alloc ()
from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0 0x00007ffff715ff1c in g_slice_alloc ()
from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff71603ea in g_slice_alloc0 ()
from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff72522f6 in g_type_create_instance ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x00007ffff7238615 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff7239b1d in g_object_new_with_properties ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007ffff723a5f1 in g_object_new ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x00005555555d9292 in ?? ()
#7 0x00005555555a56f9 in ?? ()
#8 0x00005555555ddb37 in ?? ()
#9 0x00007ffff7238306 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff723a74c in g_object_setv ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00007ffff723b42b in g_object_set_property ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x00007ffff7f769b9 in ?? () from /usr/lib/x86_64-linux-gnu/libexo-2.so.0
#13 0x00007ffff7f76aee in exo_binding_new_full ()
--Type <RET> for more, q to quit, c to continue without paging--
/libexo-2.so.0
#14 0x00007ffff7f76bd1 in exo_binding_new () from /usr/lib/x86_64-linux-gnu/libexo-2.so.0
#15 0x00007ffff72332ee in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#16 0x00007ffff724ba48 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#17 0x00007ffff724bc3f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#18 0x00007ffff7afc327 in gtk_widget_realize () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#19 0x00007ffff7aff728 in gtk_widget_set_parent () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#20 0x00007ffff79ccd69 in ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#21 0x00005555555ee75e in ?? ()
#22 0x00005555555ee93f in ?? ()
#23 0x00005555555f0d86 in ?? ()
#24 0x000055555558b312 in ?? ()
#25 0x000055555558b5d4 in ?? ()
#26 0x000055555558d4ea in ?? ()
#27 0x000055555558b9b5 in ?? ()
#28 0x000055555558bbeb in ?? ()
#29 0x00007ffff72fac15 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#30 0x00007ffff72332ee in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x00007ffff724adf9 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#32 0x00007ffff724bc3f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#33 0x00007ffff7355aa3 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#34 0x00007ffff7358329 in ?? ()Pages: 1
Board footer
