Your message dated Thu, 6 Nov 2025 18:10:28 -0500
with message-id
<CAAajCMbEGeU1s25jpEe8X6shc3ORJcSDUw=so-RFXNkWy=d...@mail.gmail.com>
and subject line closing ancient gdm3 bugs
has caused the Debian Bug report #733612,
regarding [gdm3] GDM3 Login error with vesa driver if passwor is set
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.)
--
733612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733612
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.8.4-6
Severity: important
--- Please enter the report below this line. ---
If I use vesa driver I receive correct GDM3 login screen (with nouveau I
have no correct gdm3, if interested, see bug no. 733606 of
[xserver-xorg-video-nouveau] package), and if password is inactivated (x
removed from double colons (:x:) from etc/passwd) for user I choose GDM3
starts gnome correctly and everything runs without problem. However, if
user has active password, GDM3 asks for password, then goes into a blank
grey screen without doing anything (HD led is idle) for a long time
(more than 5 mins - killing or (service) stopping gdm3 also does not
close X), then it switch back to console where character graphics are
also gone into wrong: in some cases all character spaces has fully
filled with different color (looks like a random mosaic tile picture) or
in other case each character is changed to anything other (e.g. instead
of empty (space) char a double wave, instead of Latin alphabet letters
different shapes, lines or curves, etc.).
Continuous fresh upgrade of debian testing since the last 1 month did
not solve the problem.
I have tested another debian testing install on other PCs (desktop AMD
with Nvidia FX5200 with nouveau driver and laptop Intel with ATI
Mobility Radeon 7200 with radeon driver) but this login-password error
did not occur (this is why I assumed this is vesa-specific but, as I
have written in the subject).
This login-password error occurred first after the upgrade of GDM3 from
the old (debian 7) wheezy-style to this new (debian 8) jessy-style.
I have tried to find any gdm3 log file but I did not found any. If you
need other hw, sw or log info, please write and I'll generate it/search
for it.
--- System information. ---
Architecture: i386
Kernel: Linux 3.11-2-686-pae
Debian upgrades: Squeeze-testing -> Squeeze-stable -> Wheezy-testing ->
Wheezy-stable -> Jessie-testing
Debian Release: jessie/sid
500 testing www.deb-multimedia.org
500 testing security.debian.org
500 testing ftp.hu.debian.org
--- Package information. ---
Depends (Version) | Installed
=============================================-+-================
libaccountsservice0 (>= 0.6.8) | 0.6.34-2
libatk1.0-0 (>= 1.12.4) | 2.10.0-2
libaudit1 (>= 1:2.2.1) | 1:2.3.2-2
libc6 (>= 2.4) | 2.17-97
libcairo-gobject2 (>= 1.10.0) | 1.12.16-2
libcairo2 (>= 1.2.4) | 1.12.16-2
libcanberra-gtk3-0 (>= 0.25) | 0.30-2
libcanberra0 (>= 0.2) | 0.30-2
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.28.2-1+b1
libgdm1 (= 3.8.4-6) | 3.8.4-6
libglib2.0-0 (>= 2.36.0) | 2.36.4-1
libgtk-3-0 (>= 3.0.0) | 3.8.6-1
libpam0g (>= 0.99.7.1) | 1.1.3-9
libpango-1.0-0 (>= 1.14.0) | 1.36.0-1+b1
libpangocairo-1.0-0 (>= 1.14.0) | 1.36.0-1+b1
libselinux1 (>= 1.32) | 2.2.1-1
libwrap0 (>= 7.6-4~) | 7.6.q-24
libx11-6 | 2:1.6.2-1
libxau6 | 1:1.0.8-1
libxdmcp6 | 1:1.1.1-1
libxrandr2 (>= 2:1.2.99.3) | 2:1.4.1-1
dconf-gsettings-backend (>= 0.12.1-2) | 0.18.0-1
debconf (>= 0.5) | 1.5.52
OR debconf-2.0 |
gir1.2-gdm3 (= 3.8.4-6) | 3.8.4-6
adduser | 3.113+nmu3
libpam-modules (>= 0.72-1) | 1.1.3-9
libpam-runtime (>= 0.76-13.1) | 1.1.3-9
libpam-systemd | 204-5
gnome-session-bin (>= 3.6) | 3.8.4-3
gnome-settings-daemon (>= 3.2) | 3.8.5-2
gnome-shell (>= 3.6) | 3.8.4-5
upower | 0.9.23-2+b1
gnome-session | 3.8.4-3
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) | 4.1+Debian12
librsvg2-common | 2.40.0-1
accountsservice (>= 0.6.12) | 0.6.34-2
gsettings-desktop-schemas | 3.8.2-2
libglib2.0-bin (>= 2.35.0) | 2.36.4-1
dconf-cli (>= 0.12.1-2) | 0.18.0-1
x11-common (>= 1:7.6+11) | 1:7.7+4
x11-xserver-utils | 7.7+1
Recommends (Version) | Installed
========================================-+-===========
zenity | 3.8.0-1
xserver-xephyr | 2:1.14.5-1
x11-xkb-utils | 7.7~1
xserver-xorg | 1:7.7+4
at-spi2-core | 2.10.2-1
gnome-icon-theme | 3.10.0-1
gnome-icon-theme-symbolic | 3.10.1-1
desktop-base (>= 6) | 7.0.3
Suggests (Version) | Installed
===================================-+-===========
libpam-gnome-keyring | 3.8.2-2
gnome-orca | 3.4.2-2
--- 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 ---
