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 #916704,
regarding gdm3: Black screen with coursor after login
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.)


-- 
916704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916704
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.22.3-3+deb9u2
Severity: important

Dear Maintainer,

Black screen with coursor after login.
Using lightdm solves the issue.



-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/6 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice                       0.6.43-1
ii  adduser                               3.115
ii  dconf-cli                             0.26.0-2+b1
ii  dconf-gsettings-backend               0.26.0-2+b1
ii  debconf [debconf-2.0]                 1.5.61
ii  gir1.2-gdm-1.0                        3.22.3-3+deb9u2
ii  gnome-session [x-session-manager]     3.22.3-1
ii  gnome-session-bin                     3.22.3-1
ii  gnome-settings-daemon                 3.22.2-2+deb9u2
ii  gnome-shell                           3.22.3-3
ii  gnome-terminal [x-terminal-emulator]  3.22.2-1
ii  gsettings-desktop-schemas             3.22.0-1
ii  libaccountsservice0                   0.6.43-1
ii  libaudit1                             1:2.6.7-2
ii  libc6                                 2.24-11+deb9u3
ii  libcanberra-gtk3-0                    0.30-3
ii  libcanberra0                          0.30-3
ii  libgdk-pixbuf2.0-0                    2.36.5-2+deb9u2
ii  libgdm1                               3.22.3-3+deb9u2
ii  libglib2.0-0                          2.50.3-2
ii  libglib2.0-bin                        2.50.3-2
ii  libgtk-3-0                            3.22.11-1
ii  libkeyutils1                          1.5.9-9
ii  libpam-modules                        1.1.8-3.6
ii  libpam-runtime                        1.1.8-3.6
ii  libpam-systemd                        232-25+deb9u6
ii  libpam0g                              1.1.8-3.6
ii  librsvg2-common                       2.40.16-1+b1
ii  libselinux1                           2.6-3+b3
ii  libsystemd0                           232-25+deb9u6
ii  libwrap0                              7.6.q-26
ii  libx11-6                              2:1.6.4-3+deb9u1
ii  libxau6                               1:1.0.8-1
ii  libxcb1                               1.12-1
ii  libxdmcp6                             1:1.1.2-3
ii  lsb-base                              9.20161125
ii  mutter [x-window-manager]             3.22.3-2
ii  policykit-1                           0.105-18+deb9u1
ii  ucf                                   3.0036
ii  x11-common                            1:7.7+19
ii  x11-xserver-utils                     7.7+7+b1

Versions of packages gdm3 recommends:
ii  at-spi2-core    2.22.0-6+deb9u1
ii  desktop-base    9.0.2+deb9u1
ii  x11-xkb-utils   7.7+3+b1
ii  xserver-xephyr  2:1.19.2-1+deb9u5
ii  xserver-xorg    1:7.7+19
ii  zenity          3.22.0-1+b1

Versions of packages gdm3 suggests:
pn  gnome-orca            <none>
ii  libpam-gnome-keyring  3.20.0-3

-- debconf information excluded

--- 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 ---

Reply via email to