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 #859422,
regarding gdm3: GDM3 causes login virtual terminal to hang
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.)
--
859422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859422
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.22.1-2
Severity: important
Dear Maintainer,
After upgrading from Jessie 8.7 to Stretch I encountered an issue after my
first reboot where the output on the virtual console hung on an error:
b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 12, Type 11 (AC), Revision 1)
The above errod does not bother me as I am not using wireless, so
I switched to a second vt and was at the login prompt. I was then able to login
and run startx to start xfce but straight away I got the message "Unlock Login
Keyring" - "The Login Keyring did not get unlocked
when you logged into tour computer" and to reenter my password. Subsequently
all worked ok except I was unable to lock the pc as it caused the screen to go
black and was then unable to get a login prompt from
the VT running the xsession. This may be gnome-session error or kernel issue
but changing to lightdm solved the issue.
>From syslog
pr 3 11:48:44 burma gnome-session-binary[1189]: Entering running state
Apr 3 11:48:44 burma gnome-session[1189]: Unable to init server: Could not
connect: Connection refused
Apr 3 11:48:44 burma kernel: [ 9.716343] gnome-session-f[1287]: segfault at
0 ip 00007f69368f2e09 sp 00007ffd9a053d90 error 4 in
libgtk-3.so.0.2200.9[7f6936610000+6ff000]
Apr 3 11:48:47 burma systemd[1333]: Started D-Bus User Message Bus.
Apr 3 11:48:47 burma dbus-daemon[1633]: Activating via systemd: service
name='org.a11y.Bus' unit='at-spi-dbus-bus.service'
Apr 3 11:48:47 burma systemd[1333]: Starting Accessibility services bus...
Apr 3 11:48:47 burma dbus-daemon[1633]: Successfully activated service
'org.a11y.Bus'
Apr 3 11:48:47 burma systemd[1333]: Started Accessibility services bus.
Apr 3 11:48:47 burma at-spi-bus-launcher[1640]: Activating service
name='org.a11y.atspi.Registry'
Apr 3 11:48:47 burma at-spi-bus-launcher[1640]: Successfully activated service
'org.a11y.atspi.Registry'
Apr 3 11:48:47 burma org.a11y.atspi.Registry[1645]: SpiRegistry daemon is
running with well-known name - org.a11y.atspi.Registry
Apr 3 11:48:47 burma gnome-session-binary[1635]: Entering running state
Apr 3 11:48:47 burma gnome-session[1635]: Unable to init server: Could not
connect: Connection refused
Apr 3 11:48:47 burma gnome-session[1635]: gnome-session-binary[1635]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 3 11:48:47 burma gnome-session-binary[1635]: GLib-GObject-CRITICAL:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 3 11:48:47 burma gnome-session-binary[1635]: GLib-GObject-CRITICAL:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Apr 3 11:48:47 burma kernel: [ 12.702152] gnome-session-f[1655]: segfault at
0 ip 00007f385306ce09 sp 00007ffdbf7c9080 error 4 in
libgtk-3.so.0.2200.9[7f3852d8a000+6ff000]
Apr 3 11:48:47 burma gnome-session[1635]: gnome-session-binary[1635]:
GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (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.60
ii gir1.2-gdm-1.0 3.22.1-2
ii gnome-session-bin 3.22.3-1
ii gnome-settings-daemon 3.22.2-1
ii gnome-shell 3.22.3-2
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-1
ii libc6 2.24-9
ii libcanberra-gtk3-0 0.30-3
ii libcanberra0 0.30-3
ii libgdk-pixbuf2.0-0 2.36.5-2
ii libgdm1 3.22.1-2
ii libglib2.0-0 2.50.3-2
ii libglib2.0-bin 2.50.3-2
ii libgtk-3-0 3.22.9-4
ii libkeyutils1 1.5.9-9
ii libpam-modules 1.1.8-3.5
ii libpam-runtime 1.1.8-3.5
ii libpam-systemd 232-19
ii libpam0g 1.1.8-3.5
ii librsvg2-common 2.40.16-1+b1
ii libselinux1 2.6-3+b1
ii libsystemd0 232-19
ii libwrap0 7.6.q-26
ii libx11-6 2:1.6.4-3
ii libxau6 1:1.0.8-1
ii libxdmcp6 1:1.1.2-3
ii lsb-base 9.20161125
ii metacity [x-window-manager] 1:3.22.1-1
ii mutter [x-window-manager] 3.22.3-2
ii policykit-1 0.105-17
ii terminator [x-terminal-emulator] 1.90+bzr-1705-1
ii ucf 3.0036
ii x11-common 1:7.7+18
ii x11-xserver-utils 7.7+7+b1
ii xfce4-session [x-session-manager] 4.12.1-5
ii xfce4-terminal [x-terminal-emulator] 0.8.3-1
ii xfwm4 [x-window-manager] 4.12.3-3
ii xterm [x-terminal-emulator] 327-2
Versions of packages gdm3 recommends:
ii at-spi2-core 2.22.0-5+b1
ii desktop-base 9.0.2
ii x11-xkb-utils 7.7+3+b1
ii xserver-xephyr 2:1.19.2-1
ii xserver-xorg 1:7.7+18
ii zenity 3.22.0-1+b1
Versions of packages gdm3 suggests:
ii gnome-orca 3.22.2-2
ii libpam-gnome-keyring 3.20.0-3
-- debconf information:
gdm3/daemon_name: /usr/sbin/gdm3
* shared/default-x-display-manager: lightdm
--- 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 ---
