Your message dated Thu, 6 Nov 2025 18:04:45 -0500
with message-id
<caaajcmzr+tpiylq1ykax3weok0kkilssqounu+duqnsh2_y...@mail.gmail.com>
and subject line closing ancient gdm3 bugs
has caused the Debian Bug report #681282,
regarding gdm3: gdm does not start the login window
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.)
--
681282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681282
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.4.1-2
Severity: important
Since gdm3 has been updated from 3.0.4-4 to 3.4.1-2, I cannot log into
my system anymore using gdm3. X server is started, but it stays at the
state with a black screen and an X11 clock cursor. Moving the mouse
makes the cursor move but unfortunately this is the only interaction
available.
2 workarounds:
- Switch to a console, log-in and run startx
- Downgrade gdm3 to 3.0.4-4.
I have the same problem with a different PC (amd64 and nouveau driver
are common).
I do not think I had some fancy configurations. I have tried to purge
gdm3 and to re-install it but it led to the same problem.
Antoine
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.21-5
ii adduser 3.113+nmu3
ii awesome [x-window-manager] 3.4.12-2
ii dconf-gsettings-backend 0.12.1-2
ii dconf-tools 0.12.1-2
ii debconf [debconf-2.0] 1.5.44
ii dpkg 1.16.4.3
ii e17 [x-window-manager] 0.16.999.70492-2
ii gir1.2-freedesktop 1.32.1-1
ii gir1.2-glib-2.0 1.32.1-1
ii gnome-session [x-session-manager] 3.4.2.1-1
ii gnome-session-bin 3.4.2.1-1
ii gnome-session-fallback [x-session-manager] 3.4.2.1-1
ii gnome-settings-daemon 3.4.2-3
ii gnome-terminal [x-terminal-emulator] 3.4.1.1-1
ii gsettings-desktop-schemas 3.4.2-1
ii libaccountsservice0 0.6.21-5
ii libatk1.0-0 2.4.0-2
ii libattr1 1:2.4.46-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.13-33
ii libcairo-gobject2 1.12.2-2
ii libcairo2 1.12.2-2
ii libcanberra-gtk3-0 0.28-4
ii libcanberra0 0.28-4
ii libdbus-1-3 1.6.0-1
ii libdbus-glib-1-2 0.100-1
ii libfontconfig1 2.9.0-6
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libglib2.0-bin 2.32.3-1
ii libgtk-3-0 3.4.2-2
ii libpam-modules 1.1.3-7.1
ii libpam-runtime 1.1.3-7.1
ii libpam0g 1.1.3-7.1
ii libpango1.0-0 1.30.0-1
ii librsvg2-common 2.36.1-1
ii libselinux1 2.1.9-5
ii libupower-glib1 0.9.17-1
ii libwrap0 7.6.q-23
ii libx11-6 2:1.5.0-1
ii libxau6 1:1.0.7-1
ii libxdmcp6 1:1.1.1-1
ii libxklavier16 5.2.1-1
ii libxrandr2 2:1.3.2-2
ii lsb-base 4.1+Debian7
ii metacity [x-window-manager] 1:2.34.3-2
ii policykit-1-gnome 0.105-2
ii twm [x-window-manager] 1:1.0.6-1
ii upower 0.9.17-1
ii x11-common 1:7.7+1
ii x11-xserver-utils 7.7~3
ii xfce4-session [x-session-manager] 4.8.3-2
ii xfce4-terminal [x-terminal-emulator] 0.4.8-1+b1
ii xfwm4 [x-window-manager] 4.8.3-1
ii xterm [x-terminal-emulator] 278-1
Versions of packages gdm3 recommends:
ii desktop-base 7.0.0
ii gnome-icon-theme 3.4.0-2
ii libatk-adaptor [at-spi] 2.5.3-1
ii x11-xkb-utils 7.7~1
ii xserver-xephyr 2:1.12.1.902-1
ii xserver-xorg 1:7.7+1
ii zenity 3.4.0-2
Versions of packages gdm3 suggests:
ii gnome-mag 1:0.16.3-1
ii gnome-orca 3.4.2-2
ii gnome-shell 3.4.1-8
ii gok 2.30.0-1
ii libpam-gnome-keyring 3.4.1-4
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
signature.asc
Description: Digital signature
--- 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ích
--- End Message ---
