Forum: >>> Magnum BBS <<<

Re: Trixie xorg crash (was: Trixie hangs during boot after upgrade) (1/

From Rainer Dorsch@21:1/5 to All on Mon Jun 23 23:59:11 2025

This is a multi-part message in MIME format.

--nextPart10682264.nUPlyArG6x
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Am Freitag, 20. Juni 2025, 23:33:28 Mitteleuropäische Sommerzeit schrieb Rainer Dorsch:

Am Donnerstag, 19. Juni 2025, 16:40:30 Mitteleuropäische Sommerzeit schrieb

Rainer Dorsch:

Am Donnerstag, 19. Juni 2025, 16:22:17 Mitteleuropäische Sommerzeit schrieb

Rainer Dorsch:

Am Donnerstag, 19. Juni 2025, 15:38:46 Mitteleuropäische Sommerzeit schrieb

Rainer Dorsch:

Hi,

I upgraded to Trixie some weeks back and had no serious issues during all
upgrades so far. After the upgrade today, I rebooted and the Trixie system
failed to boot. I still can open a root shell if I boot into recovery mode.

Is there currently a know Trixie issue, which is causing this?

Photos of the boot messages, if I do a

- regular boot
https://nc.d5x.de/index.php/s/C9jLJJTEJTTyXFi

- enter recovery mode:
https://nc.d5x.de/index.php/s/S7jeSkB7667bYRJ

Since the last messages I see are networking messages, I use /etc/network/
interfaces to configure my network (which contains a number of VLANs). In
the root shell, the network is not yet up and running.

Any hint or advice how to fix or debug this issue is welcome.

I got rid of all the nvidia stuff (my systems don't have nvidia
hardware)
and diagnosed it to be not a boot issue, but an sddm/xorg issue:

● sddm.service - Simple Desktop Display Manager

Loaded: loaded (/usr/lib/systemd/system/sddm.service; enabled;

preset:

enabled)

Active: active (running) since Thu 2025-06-19 16:16:57 CEST; 45s
ago

Invocation: e9c9f849bc47481da2d987ea2f5fd5ab

Docs: man:sddm(1)

man:sddm.conf(5)

Main PID: 1930 (sddm)

Tasks: 2 (limit: 38044)

Memory: 89.5M (peak: 100.9M)

CPU: 191ms

CGroup: /system.slice/sddm.service

└─1930 /usr/bin/sddm

Jun 19 16:16:57 h370 sddm[1930]: Loaded empty theme configuration
Jun 19 16:16:57 h370 sddm[1930]: Xauthority path: "/run/sddm/xauth_josBoJ"
Jun 19 16:16:57 h370 sddm[1930]: Using VT 2
Jun 19 16:16:57 h370 sddm[1930]: Display server starting...
Jun 19 16:16:57 h370 sddm[1930]: Writing cookie to "/run/sddm/xauth_josBoJ"
Jun 19 16:16:57 h370 sddm[1930]: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt2 -auth /run/sddm/xauth_josBoJ -noreset -displayfd 16 Jun 19 16:16:58 h370 systemd-coredump[2354]: Process 2256 (Xorg) of user 0 dumped core.

Module libgcc_s.so.1 from
deb

gcc-14-14.2.0-19.amd64

Module libstdc++.so.6 from
deb

gcc-14-14.2.0-19.amd64

Module libzstd.so.1 from
deb

libzstd-1.5.7+dfsg-1.amd64

Module libsystemd.so.0 from
deb

systemd-257.6-1.amd64

Module libudev.so.1 from
deb

systemd-257.6-1.amd64

Stack trace of thread 2256:
#0 0x00007f0a7bb3b507

__GI_abort (libc.so.6 + 0x28507)

#1 0x0000557bff22fba0
OsAbort

(/ usr/lib/xorg/Xorg + 0x1e4ba0)

#2 0x0000557bff235479 n/a

(/usr/ lib/xorg/Xorg + 0x1ea479)

#3 0x0000557bff236579

FatalError (/usr/lib/xorg/Xorg + 0x1eb579)

#4 0x0000557bff22cd09 n/a

(/usr/ lib/xorg/Xorg + 0x1e1d09)

#5 0x00007f0a7bb52df0

__restore_rt (libc.so.6 + 0x3fdf0)

#6 0x00007f0a7bba795c

__pthread_kill_implementation (libc.so.6 + 0x9495c)

#7 0x00007f0a7bb52cc2

__GI_raise (libc.so.6 + 0x3fcc2)

#8 0x00007f0a7bb3b4ac

__GI_abort (libc.so.6 + 0x284ac)

#9 0x00007f0a7b72a83a n/a

(libepoxy.so.0 + 0xc283a)

#10 0x00007f0a7b72add5 n/a

(libepoxy.so.0 + 0xc2dd5)

#11 0x00007f0a7b722bde n/a

(libepoxy.so.0 + 0xbabde)

#12 0x00007f0a7b72532f n/a

(libepoxy.so.0 + 0xbd32f)

#13 0x00007f0a7b72b41c

epoxy_has_egl_extension (libepoxy.so.0 + 0xc341c)

#14 0x00007f0a7b7d9d61

glamor_egl_init (libglamoregl.so + 0x9d61)

#15 0x00007f0a7c1bde80 n/a

(modesetting_drv.so + 0xbe80)

#16 0x0000557bff0f4093

InitOutput (/usr/lib/xorg/Xorg + 0xa9093)

#17 0x0000557bff0b3ace n/a

(/usr/ lib/xorg/Xorg + 0x68ace)

#18 0x00007f0a7bb3cca8

__libc_start_call_main (libc.so.6 + 0x29ca8)

#19 0x00007f0a7bb3cd65

__libc_start_main_impl (libc.so.6 + 0x29d65)

#20 0x0000557bff09c641
_start

(/ usr/lib/xorg/Xorg + 0x51641)

Stack trace of thread 2343:
#0 0x00007f0a7bbad9ee

__syscall_cancel_arch (libc.so.6 + 0x9a9ee)

#1 0x00007f0a7bba2668

__internal_syscall_cancel (libc.so.6 + 0x8f668)

#2 0x00007f0a7bba2c9c

__futex_abstimed_wait_common64 (libc.so.6 + 0x8fc9c)

#3 0x00007f0a7bba5158

__pthread_cond_wait_common (libc.so.6 + 0x92158)

#4 0x00007f0a78fafbdd n/a

(libgallium-25.0.5-2.so + 0x5afbdd)

#5 0x00007f0a78f7b22b n/a

(libgallium-25.0.5-2.so + 0x57b22b)

#6 0x00007f0a78fafb0b n/a

(libgallium-25.0.5-2.so + 0x5afb0b)

#7 0x00007f0a7bba5b7b

start_thread (libc.so.6 + 0x92b7b)

#8 0x00007f0a7bc237b8
__clone3

(libc.so.6 + 0x1107b8)

Stack trace of thread 2342:
#0 0x00007f0a7bbad9ee

__syscall_cancel_arch (libc.so.6 + 0x9a9ee)

#1 0x00007f0a7bba2668

__internal_syscall_cancel (libc.so.6 + 0x8f668)

#2 0x00007f0a7bba2c9c

__futex_abstimed_wait_common64 (libc.so.6 + 0x8fc9c)

#3 0x00007f0a7bba5158

__pthread_cond_wait_common (libc.so.6 + 0x92158)

#4 0x00007f0a78fafbdd n/a

(libgallium-25.0.5-2.so + 0x5afbdd)

#5 0x00007f0a78f7b22b n/a

(libgallium-25.0.5-2.so + 0x57b22b)

#6 0x00007f0a78fafb0b n/a

(libgallium-25.0.5-2.so + 0x5afb0b)

#7 0x00007f0a7bba5b7b

start_thread (libc.so.6 + 0x92b7b)

#8 0x00007f0a7bc237b8
__clone3

(libc.so.6 + 0x1107b8)

ELF object binary

architecture:

AMD x86-64
Jun 19 16:16:58 h370 sddm[1930]: Failed to read display number from pipe Jun 19 16:16:58 h370 sddm[1930]: Display server stopping...
Jun 19 16:16:58 h370 sddm[1930]: Attempt 1 starting the Display server
on
vt 2 failed

Boot process looks otherwise ok.

More data of the xorg crash:

root@h370:~# tail -50 /var/log/Xorg.0.log
[ 59.562] (II) modeset(0): Creating default Display subsection in
Screen
section

"Default Screen Section" for depth/fbbpp 24/32

[ 59.562] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[ 59.562] (==) modeset(0): RGB weight 888
[ 59.562] (==) modeset(0): Default visual is TrueColor
[ 59.562] (II) Loading sub module "glamoregl"
[ 59.562] (II) LoadModule: "glamoregl"
[ 59.562] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 59.574] (II) Module glamoregl: vendor="X.Org Foundation"
[ 59.574] compiled for 1.21.1.16, module version = 1.0.1
[ 59.574] ABI class: X.Org ANSI C Emulation, version 0.4
[ 60.169] (EE)
[ 60.169] (EE) Backtrace:
[ 60.175] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.175] (EE) 0: /usr/lib/xorg/Xorg (?+0x0) [0x557bff22ccad]
[ 60.208] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.208] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f0a7bb52df0] [ 60.210] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (__pthread_kill_implementation+0x10c) [0x7f0a7bba795c]
[ 60.212] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (__GI_raise+0x12) [0x7f0a7bb52cc2]
[ 60.214] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (__GI_abort+0x22) [0x7f0a7bb3b4ac]
[ 60.215] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.215] (EE) 5: /lib/x86_64-linux-gnu/libepoxy.so.0 (?+0x0) [0x7f0a7b72a83a]
[ 60.216] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.216] (EE) 6: /lib/x86_64-linux-gnu/libepoxy.so.0 (?+0x0) [0x7f0a7b72add5]
[ 60.218] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.218] (EE) 7: /lib/x86_64-linux-gnu/libepoxy.so.0 (?+0x0) [0x7f0a7b722bde]
[ 60.219] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.219] (EE) 8: /lib/x86_64-linux-gnu/libepoxy.so.0 (?+0x0) [0x7f0a7b72532f]
[ 60.220] (EE) 9: /lib/x86_64-linux-gnu/libepoxy.so.0 (epoxy_has_egl_extension+0x1c) [0x7f0a7b72b41c]
[ 60.223] (EE) 10: /usr/lib/xorg/modules/libglamoregl.so (glamor_egl_init+0x81) [0x7f0a7b7d9d61]
[ 60.225] (EE) unw_get_proc_name failed: no unwind info found [-10]
[ 60.225] (EE) 11: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7f0a7c1bde80]
[ 60.225] (EE) 12: /usr/lib/xorg/Xorg (InitOutput+0x983) [0x557bff0f4093] [ 60.226] (EE) unw_get_proc_name failed: no unwind
info found [-10] [ 60.226] (EE) 13: /usr/lib/xorg/Xorg (?+0x0) [0x557bff0b3ace]
[ 60.227] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_call_main+0x78) [0x7f0a7bb3cca8]
[ 60.228] (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main_alias_2+0x85) [0x7f0a7bb3cd65]
[ 60.229] (EE) 16: /usr/lib/xorg/Xorg (_start+0x21) [0x557bff09c641]
[ 60.229] (EE)
[ 60.229] (EE)
Fatal server error:
[ 60.229] (EE) Caught signal 6 (Aborted). Server aborting
[ 60.229] (EE)
[ 60.229] (EE)
Please consult the The X.Org Foundation support

at http://wiki.x.org

for help.

[ 60.229] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 60.229] (EE)
[ 60.292] (EE) Server terminated with error (1). Closing log file. root@h370:~# lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation CoffeeLake-S GT2 [UHD Graphics 630]

DeviceName: Onboard - Video
Subsystem: ASUSTeK Computer Inc. Device 8694
Kernel driver in use: i915

root@h370:~#

Is there a way to disable glamoregl to verify that this is causing the issue?

lightdm shows the same issue. Can anybody tell which is the right package to report this bug against?

It seems that symlinks have been missing:

root@h370:/usr/lib/x86_64-linux-gnu# ln -s libGL.so libGL.so.1 root@h370:/usr/lib/x86_64-linux-gnu# ln -s libEGL.so libEGL.so.1 root@h370:/usr/lib/x86_64-linux-gnu#

cures the issue.

The symlinks resolve to
root@h370:/usr/lib/x86_64-linux-gnu# ls -l libEGL.so.1
lrwxrwxrwx 1 root root 9 23. Jun 22:50 libEGL.so.1 -> libEGL.so root@h370:/usr/lib/x86_64-linux-gnu# ls -l libEGL.so
lrwxrwxrwx 1 root root 49 29. Okt 2024 libEGL.so -> /etc/alternatives/glx-- libEGL.so-x86_64-linux-gnu
root@h370:/usr/lib/x86_64-linux-gnu# ls -l /etc/alternatives/glx--libEGL.so- x86_64-linux-gnu
lrwxrwxrwx 1 root root 49 29. Okt 2024 /etc/alternatives/glx--libEGL.so- x86_64-linux-gnu -> /usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so root@h370:/usr/lib/x86_64-linux-gnu# ls -l /usr/lib/mesa-diverted/x86_64- linux-gnu/libEGL.so
lrwxrwxrwx 1 root root 11 29. Okt 2024 /usr/lib/mesa-diverted/x86_64-linux- gnu/libEGL.so -> libEGL.so.1
root@h370:/usr/lib/x86_64-linux-gnu#

Did maybe an update-alternatives during an upgrade go wrong?

Has anybody an explanation what could have caused this?

Thanks
Rainer

--
Rainer Dorsch
http://bokomoko.de/
--nextPart10682264.nUPlyArG6x
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>Am Freitag, 20. Juni 2025, 23:33:28 Mitteleuropäische Sommerzeit schrieb Rainer Dorsch:
> Am Donnerstag, 19. Juni 2025, 16:40:30 Mitteleuropäische Sommerzeit schrieb
> > Rainer Dorsch:
> > Am Donnerstag, 19. Juni 2025, 16:22:17 Mitteleuropäische Sommerzeit
> > schrieb
<p style="margin-to

Who's Online
Recent Visitors
- Plume
  Sun Sep 14 09:34:52 2025
  from Uk via Raw
- Gretchiie
  Sun Sep 14 06:07:30 2025
  from Derry, Nh via Telnet
- Thlc
  Sat Sep 13 17:11:34 2025
  from Rognac, France via Telnet
- Thlc
  Sat Sep 13 17:04:03 2025
  from Rognac, France via Telnet
- Thlc
  Sat Sep 13 16:32:19 2025
  from Rognac, France via SSH
- Thlc
  Sat Sep 13 15:41:11 2025
  from Rognac, France via SSH
- Thlc
  Sat Sep 13 07:56:03 2025
  from Rognac, France via SSH
- Gretchiie
  Sat Sep 13 07:22:10 2025
  from Derry, Nh via Telnet

System Info

Sysop:	Keyop
Location:	Huddersfield, West Yorkshire, UK
Users:	546
Nodes:	16 (0 / 16)
Uptime:	162:38:56
Calls:	10,385
Calls today:	2
Files:	14,057
Messages:	6,416,502

Re: Trixie xorg crash (was: Trixie hangs during boot after upgrade) (1/

Who's Online

Recent Visitors

System Info