Your message dated Thu, 6 Nov 2025 19:02:35 -0500
with message-id
<CAAajCMbQjMZ7G_Z3xrQWuNDPWLjuAM169oCkMRCqdeKond=t...@mail.gmail.com>
and subject line closing old gdm3 bugs
has caused the Debian Bug report #898147,
regarding gdm3: fails to start: ("Oops! A problem has occured!" screen)
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.)
--
898147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898147
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gdm3
Version: 3.28.1-1
--- Please enter the report below this line. ---
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate
***
* What led up to the situation?
Installed GDM3.
* What exactly did you do (or not do) that was effective (or
ineffective)?
For now, just started to do some debugging... (I copy the output of
relevant systemd-related commands below.)
From what I could see in the log (journalctl), it seems to have something
to do with GLibC...
However, I don't know to which glibc/gdm3 version to downgrade to, as I
have all packages from testing...
* What was the outcome of this action?
When booting, GDM3 fails to start. It gives me the "Oops! A problem has
occured!" screen.
The system boots OK with both SDDM and LightDM.
* What outcome did you expect instead?
GDM to start correctly.
* Additional logs:
Here is the output of relevant systemd-related commands ("systemctl" and
"journalctl").
#systemctl status gdm3
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor
preset:
enabled)
Active: active (running) since Mon 2018-05-07 13:12:30 -03; 22min ago
Main PID: 704 (gdm3)
Tasks: 3 (limit: 4915)
Memory: 8.0M
CGroup: /system.slice/gdm.service
└─704 /usr/sbin/gdm3
May 07 13:33:21 berlin gdm3[704]: Child process -1061 was already dead.
May 07 13:33:21 berlin gdm3[704]: Child process 1046 was already dead.
May 07 13:33:21 berlin gdm3[704]: Unable to kill session worker process
May 07 13:33:21 berlin gdm-launch-environment][1670]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:33:21 berlin gdm-launch-environment][1670]:
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
May 07 13:33:21 berlin gdm3[704]: GdmDisplay: display lasted 0.294573
seconds
May 07 13:33:21 berlin gdm3[704]: Child process -1691 was already dead.
May 07 13:33:21 berlin gdm3[704]: Child process 1670 was already dead.
May 07 13:33:21 berlin gdm3[704]: Unable to kill session worker process
May 07 13:33:21 berlin gdm-launch-environment][1708]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
********************
#journalctl -rx --unit=gdm
-- Logs begin at Mon 2018-05-07 13:12:28 -03, end at Mon 2018-05-07
13:39:32 -03. --
May 07 13:39:23 berlin gdm-launch-environment][1818]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:39:23 berlin gdm3[1792]: Unable to kill session worker process
May 07 13:39:23 berlin gdm3[1792]: Child process 1796 was already dead.
May 07 13:39:23 berlin gdm3[1792]: Child process -1800 was already dead.
May 07 13:39:23 berlin gdm3[1792]: GLib: g_variant_new_string: assertion
'string != NULL' failed
May 07 13:39:23 berlin gdm3[1792]: GdmDisplay: display lasted 0.477945
seconds
May 07 13:39:23 berlin gdm-launch-environment][1796]:
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
May 07 13:39:23 berlin gdm-launch-environment][1796]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:39:23 berlin systemd[1]: Started GNOME Display Manager.
-- Subject: Unit gdm.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has finished starting up.
--
-- The start-up result is RESULT.
May 07 13:39:23 berlin systemd[1]: Starting GNOME Display Manager...
-- Subject: Unit gdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has begun starting up.
May 07 13:39:23 berlin systemd[1]: Stopped GNOME Display Manager.
-- Subject: Unit gdm.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has finished shutting down.
May 07 13:39:22 berlin gdm3[704]: GLib: g_hash_table_find: assertion
'version == hash_table->version' failed
May 07 13:39:22 berlin gdm3[704]: GLib: g_variant_new_string: assertion
'string != NULL' failed
May 07 13:39:22 berlin gdm3[704]: GLib: g_variant_new_string: assertion
'string != NULL' failed
May 07 13:39:22 berlin systemd[1]: Stopping GNOME Display Manager...
-- Subject: Unit gdm.service has begun shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has begun shutting down.
May 07 13:33:21 berlin gdm-launch-environment][1708]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:33:21 berlin gdm3[704]: Unable to kill session worker process
May 07 13:33:21 berlin gdm3[704]: Child process 1670 was already dead.
May 07 13:33:21 berlin gdm3[704]: Child process -1691 was already dead.
May 07 13:33:21 berlin gdm3[704]: GdmDisplay: display lasted 0.294573
seconds
May 07 13:33:21 berlin gdm-launch-environment][1670]:
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
May 07 13:33:21 berlin gdm-launch-environment][1670]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:33:21 berlin gdm3[704]: Unable to kill session worker process
May 07 13:33:21 berlin gdm3[704]: Child process 1046 was already dead.
May 07 13:33:21 berlin gdm3[704]: Child process -1061 was already dead.
May 07 13:14:19 berlin gdm-launch-environment][1046]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:14:19 berlin gdm3[704]: Unable to kill session worker process
May 07 13:14:19 berlin gdm3[704]: Child process 1013 was already dead.
May 07 13:14:19 berlin gdm3[704]: Child process -1028 was already dead.
May 07 13:14:19 berlin gdm3[704]: GdmDisplay: display lasted 0.346126
seconds
May 07 13:14:19 berlin gdm-launch-environment][1013]:
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
May 07 13:14:18 berlin gdm-launch-environment][1013]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:14:18 berlin gdm3[704]: Unable to kill session worker process
May 07 13:14:18 berlin gdm3[704]: Child process 968 was already dead.
May 07 13:14:18 berlin gdm3[704]: Child process -996 was already dead.
May 07 13:14:03 berlin gdm-launch-environment][968]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:14:03 berlin gdm3[704]: Unable to kill session worker process
May 07 13:14:03 berlin gdm3[704]: Child process 955 was already dead.
May 07 13:14:03 berlin gdm3[704]: Child process -959 was already dead.
May 07 13:13:38 berlin gdm-launch-environment][955]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:13:38 berlin gdm3[704]: Unable to kill session worker process
May 07 13:13:38 berlin gdm3[704]: Child process 936 was already dead.
May 07 13:13:38 berlin gdm3[704]: Child process -946 was already dead.
May 07 13:13:13 berlin gdm-launch-environment][936]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:13:13 berlin gdm3[704]: Unable to kill session worker process
May 07 13:13:13 berlin gdm3[704]: Child process 912 was already dead.
May 07 13:13:13 berlin gdm3[704]: Child process -927 was already dead.
May 07 13:12:48 berlin gdm-launch-environment][912]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:12:48 berlin gdm3[704]: Unable to kill session worker process
May 07 13:12:48 berlin gdm3[704]: Child process 779 was already dead.
May 07 13:12:48 berlin gdm3[704]: Child process -795 was already dead.
May 07 13:12:33 berlin gdm-launch-environment][779]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:12:33 berlin gdm3[704]: Unable to kill session worker process
May 07 13:12:33 berlin gdm3[704]: Child process 711 was already dead.
May 07 13:12:33 berlin gdm3[704]: Child process -729 was already dead.
May 07 13:12:33 berlin gdm3[704]: GdmDisplay: display lasted 2.267034
seconds
May 07 13:12:33 berlin gdm-launch-environment][711]:
pam_unix(gdm-launch-environment:session): session closed for user Debian-gdm
May 07 13:12:32 berlin gdm-launch-environment][711]:
pam_unix(gdm-launch-environment:session): session opened for user
Debian-gdm by (uid=0)
May 07 13:12:30 berlin systemd[1]: Started GNOME Display Manager.
-- Subject: Unit gdm.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has finished starting up.
--
-- The start-up result is RESULT.
May 07 13:12:30 berlin systemd[1]: Starting GNOME Display Manager...
-- Subject: Unit gdm.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit gdm.service has begun starting up.
********************************************************
--- System information. ---
Architecture:
Kernel: Linux 4.15.0-3-amd64
Debian Release: buster/sid
900 testing deb.debian.org
500 unstable deb.debian.org
--- Package information. ---
Depends (Version) | Installed
============================================-+-===============
libaccountsservice0 (>= 0.6.37) | 0.6.45-1
libaudit1 (>= 1:2.2.1) | 1:2.8.2-1
libc6 (>= 2.14) | 2.27-3
libcanberra-gtk3-0 (>= 0.25) | 0.30-6
libcanberra0 (>= 0.2) | 0.30-6
libgdk-pixbuf2.0-0 (>= 2.22.0) | 2.36.11-2
libgdm1 (= 3.28.1-1) | 3.28.1-1
libglib2.0-0 (>= 2.39.4) | 2.56.1-2
libgtk-3-0 (>= 3.0.0) | 3.22.29-3
libkeyutils1 (>= 1.5.9) | 1.5.9-9.2
libpam0g (>= 0.99.7.1) | 1.1.8-3.7
libselinux1 (>= 1.32) | 2.7-2+b2
libsystemd0 | 238-4
libwrap0 (>= 7.6-4~) | 7.6.q-27
libx11-6 | 2:1.6.5-1
libxau6 | 1:1.0.8-1+b2
libxcb1 | 1.13-1
libxdmcp6 | 1:1.1.2-3
debconf (>= 0.5) | 1.5.66
OR debconf-2.0 |
gir1.2-gdm-1.0 (= 3.28.1-1) | 3.28.1-1
adduser | 3.117
libpam-modules (>= 0.72-1) | 1.1.8-3.7
libpam-runtime (>= 0.76-13.1) | 1.1.8-3.7
libpam-systemd | 238-4
gnome-session-bin (>= 3.10) | 3.28.1-1
gnome-settings-daemon (>= 3.24) | 3.28.1-1
gnome-shell (>= 3.19.92) | 3.28.0-1+b1
gnome-session |
OR x-session-manager |
OR x-window-manager |
OR x-terminal-emulator |
lsb-base (>= 3.2-14) | 9.20170808
librsvg2-common | 2.40.20-2
accountsservice (>= 0.6.35) | 0.6.45-1
policykit-1 (>= 0.105-5~) | 0.105-20
gsettings-desktop-schemas | 3.28.0-1
libglib2.0-bin (>= 2.35.0) | 2.56.1-2
dconf-cli (>= 0.20) | 0.28.0-2
dconf-gsettings-backend (>= 0.20) | 0.28.0-2
ucf | 3.0038
x11-common (>= 1:7.6+11) | 1:7.7+19
x11-xserver-utils | 7.7+8
Recommends (Version) | Installed
=============================-+-===========
zenity | 3.28.1-1
xserver-xephyr | 2:1.19.6-1
x11-xkb-utils | 7.7+4
xserver-xorg | 1:7.7+19
at-spi2-core | 2.28.0-2
desktop-base (>= 6) | 9.0.5
Suggests (Version) | Installed
=====================================-+-=============
libpam-gnome-keyring | 3.28.0.2-1
gnome-orca |
libpam-fprintd (>= 0.8.0-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 ---
