Your message dated Thu, 6 Nov 2025 18:16:44 -0500
with message-id
<caaajcmacrwvjkig+pho7tq88hwgrsvkkf0mj3eickup_1h1...@mail.gmail.com>
and subject line closing old gdm3 bugs
has caused the Debian Bug report #959432,
regarding gdm3: server crashes after 90 seconds frozen on Wayland
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
959432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959432
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.34.1-3
Severity: important
As I reported on #958025, after I upgraded my Sid from GNOME Shell 3.34 to 3.36
on my Surface Pro 5, every time I try to start up my system, GDM stays waiting
for 90 seconds with a frozen black screen and cursor, then it restarts itself.
I have `[debug] Enable=true` set. The system logs don't show up any useful
information (there's a 90 second gap, then it just goes into Xorg as it nothing
had happened), but I found a core dump that reports the following:
> Core was generated by `/usr/bin/Xwayland :1024 -rootless -terminate -accessx
-core -listen 4 -listen 5'.
> Program terminated with signal SIGABRT, Aborted.
> #0 0x00007f1cca11d7bb in ?? ()
> (gdb) bt
> #0 0x00007f1cca11d7bb in ?? ()
> #1 0x000000000a392000 in ?? ()
> #2 0x0000000000000000 in ?? ()
Might also be an issue with AT-SPI, but I have libatspi2.0-0 version 2.36.0-2
and the issue persists.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.18-surface (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gdm3 depends on:
ii accountsservice 0.6.55-1
ii adduser 3.118
ii dconf-cli 0.36.0-1
ii dconf-gsettings-backend 0.36.0-1
ii debconf [debconf-2.0] 1.5.74
ii gir1.2-gdm-1.0 3.34.1-3
ii gnome-session [x-session-manager] 3.36.0-2
ii gnome-session-bin 3.36.0-2+b1
ii gnome-settings-daemon 3.36.1-1
ii gnome-shell 3.36.1+git20200417-1
ii gnome-terminal [x-terminal-emulator] 3.36.2-1
ii gsettings-desktop-schemas 3.36.0-1
ii libaccountsservice0 0.6.55-1
ii libaudit1 1:2.8.5-3+b1
ii libc6 2.30-4
ii libcanberra-gtk3-0 0.30-7
ii libcanberra0 0.30-7
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-4
ii libgdm1 3.34.1-3
ii libglib2.0-0 2.64.2-1
ii libglib2.0-bin 2.64.2-1
ii libgtk-3-0 3.24.18-1
ii libkeyutils1 1.6.1-2
ii libpam-modules 1.3.1-5
ii libpam-runtime 1.3.1-5
ii libpam-systemd 245.5-2
ii libpam0g 1.3.1-5
ii librsvg2-common 2.48.3-1
ii libselinux1 3.0-1+b3
ii libsystemd0 245.5-2
ii libwrap0 7.6.q-30
ii libx11-6 2:1.6.9-2
ii libxau6 1:1.0.8-1+b2
ii libxcb1 1.14-2
ii libxdmcp6 1:1.1.2-3
ii lsb-base 11.1.0
ii mutter [x-window-manager] 3.36.1+git20200419-1
ii policykit-1 0.105-26
ii procps 2:3.3.16-4
ii ucf 3.0038+nmu1
ii x11-common 1:7.7+20
ii x11-xserver-utils 7.7+8
ii xterm [x-terminal-emulator] 354-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.36.0-2
ii desktop-base 10.0.3
ii x11-xkb-utils 7.7+5
ii xserver-xephyr 2:1.20.8-2
ii xserver-xorg 1:7.7+20
ii zenity 3.32.0-5
Versions of packages gdm3 suggests:
pn gnome-orca <none>
pn libpam-fprintd <none>
ii libpam-gnome-keyring 3.36.0-1
-- Configuration Files:
/etc/gdm3/daemon.conf changed [not included]
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
There have been many changes to Debian since this bug was originally
reported. If you are still experiencing this issue with Debian 13 (or
with Debian 12 or Testing or Unstable), please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
