Bug#1009977: gdm3: Fails to start since 2022/04/19 on Debian/testing
Adrian Immanuel Kiess
Version: 42.0-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Upgrading my Debian/testing installation on 2022/04/19
* What exactly did you do (or not do) that was effective (or
ineffective)?
# apt -u dist-upgrade
* What was the outcome of this action?
GDM3 fails to start after system loaded
* What outcome did you expect instead?
GDM3 loading fine and present login screen
since 2022/04/19, after a regular system update on my Debian/testing
installation,
GDM3 fails to load, after bringing up the system.
A curser on the upper left, top part of the screen is blinking and nothing is
happening afterwards. My GDM3 configuration is the same as before.
I have to manually login as root (CTRL+ALT+F[x]) and issue # service gdm3 stop.
Running then startx as normal user works still fine.
Maybe Wayland is broken, due to GDM3 can't load.
Thank you very much for your kind attention.
Sincerely,
Adrian Kieß
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gdm3 depends on:
ii 9wm [x-window-manager] 1.4.1-1
ii accountsservice 22.07.5-1
ii adduser 3.121
ii aewm [x-window-manager] 1.3.12-7
ii aewm++ [x-window-manager] 1.1.2-5.2
ii afterstep [x-window-manager] 2.2.12-15
ii amiwm [x-window-manager] 0.21pl2-2
ii blackbox [x-window-manager] 0.70.1-38
ii ctwm [x-window-manager] 4.0.3-1
ii dbus [default-dbus-system-bus] 1.14.0-1
ii dbus-bin 1.14.0-1
ii dbus-daemon 1.14.0-1
ii dconf-cli 0.40.0-3
ii dconf-gsettings-backend 0.40.0-3
ii debconf [debconf-2.0] 1.5.79
ii deepin-terminal [x-terminal-emulator] 5.2.11-1
ii dwm [x-window-manager] 6.3-0.1
ii enlightenment [x-window-manager] 0.25.3-1
ii fluxbox [x-window-manager] 1.3.5-2.1
ii fvwm [x-window-manager] 1:2.6.8-1+b2
ii fvwm-crystal [x-window-manager] 3.4.1+dfsg-3
ii gir1.2-gdm-1.0 42.0-1
ii gnome-session [x-session-manager] 42.0-1
ii gnome-session-bin 42.0-1
ii gnome-session-common 42.0-1
ii gnome-session-flashback [x-session-manager] 3.44.0-1
ii gnome-settings-daemon 42.1-3
ii gnome-shell 42.0-3
ii gnome-terminal [x-terminal-emulator] 3.44.0-1
ii gsettings-desktop-schemas 42.0-1
ii jwm [x-window-manager] 2.4.1-1
ii kwin-x11 [x-window-manager] 4:5.24.4-1
ii libaccountsservice0 22.07.5-1
ii libaudit1 1:3.0.7-1+b1
ii libc6 2.33-7
ii libcanberra-gtk3-0 0.30-10
ii libcanberra0 0.30-10
ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii libgdm1 42.0-1
ii libglib2.0-0 2.72.1-1
ii libglib2.0-bin 2.72.1-1
ii libgtk-3-0 3.24.33-1
ii libgudev-1.0-0 237-2
ii libkeyutils1 1.6.1-3
ii libpam-modules 1.4.0-11
ii libpam-runtime 1.4.0-11
ii libpam-systemd [logind] 250.4-1
ii libpam0g 1.4.0-11
ii librsvg2-common 2.52.5+dfsg-3+b1
ii libselinux1 3.3-1+b2
ii libsystemd0 250.4-1
ii libx11-6 2:1.7.5-1
ii libxau6 1:1.0.9-1
ii libxcb1 1.14-3
ii libxdmcp6 1:1.1.2-3
ii lsb-base 11.1.0
ii lxsession [x-session-manager] 0.5.5-2+b1
ii marco [x-window-manager] 1.26.0-2
ii mate-session-manager [x-session-manager] 1.26.0-1
ii mate-terminal [x-terminal-emulator] 1.26.0-1
ii metacity [x-window-manager] 1:3.44.0-1
ii miwm [x-window-manager] 1.1-8
ii mrxvt [x-terminal-emulator] 0.5.4-2
ii mutter [x-window-manager] 42.0-3
ii mwm [x-window-manager] 2.3.8-3
ii openbox [x-window-manager] 3.6.1-10
ii openbox-lxde-session [x-session-manager] 0.99.2-4
ii policykit-1 0.105-33
ii procps 2:3.3.17-7+b1
ii rxvt-unicode [x-terminal-emulator] 9.30-2+b2
ii sawfish [x-window-manager] 1:1.11.90-1.2
ii systemd-sysv 250.4-1
ii terminology [x-terminal-emulator] 1.12.1-2
ii tilix [x-terminal-emulator] 1.9.4-2+b1
ii ucf 3.0043
ii w9wm [x-window-manager] 0.4.2-8+b1
ii wmaker [x-window-manager] 0.95.9-3
ii x11-common 1:7.7+23
ii x11-xserver-utils 7.7+9
ii xfce4-session [x-session-manager] 4.16.0-1
ii xfce4-terminal [x-terminal-emulator] 0.8.10-1
ii xfwm4 [x-window-manager] 4.16.1-1
ii xterm [x-terminal-emulator] 372-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.44.0-3
ii desktop-base 11.0.3
ii gnome-session [x-session-manager] 42.0-1
ii gnome-session-flashback [x-session-manager] 3.44.0-1
ii lxsession [x-session-manager] 0.5.5-2+b1
ii mate-session-manager [x-session-manager] 1.26.0-1
ii openbox [x-session-manager] 3.6.1-10
ii openbox-lxde-session [x-session-manager] 0.99.2-4
ii x11-xkb-utils 7.7+5
ii xfce4-session [x-session-manager] 4.16.0-1
ii xserver-xephyr 2:21.1.3-2+b1
ii xserver-xorg 1:7.7+23
ii zenity 3.42.0-1
Versions of packages gdm3 suggests:
pn libpam-fprintd <none>
ii libpam-gnome-keyring 40.0-3
ii libpam-pkcs11 0.6.11-4+b1
pn libpam-sss <none>
ii orca 42.0-1
-- Configuration Files:
/etc/gdm3/daemon.conf changed:
[daemon]
[security]
AllowRoot=true
[xdmcp]
[chooser]
[debug]
/etc/pam.d/gdm-password changed:
auth requisite pam_nologin.so
@include common-auth
auth optional pam_gnome_keyring.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
session required pam_loginuid.so
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
session optional pam_keyinit.so force revoke
session required pam_limits.so
session required pam_env.so readenv=1
session required pam_env.so readenv=1 envfile=/etc/default/locale
@include common-session
session optional pam_gnome_keyring.so auto_start
@include common-password
-- debconf information:
* shared/default-x-display-manager: gdm3
gdm3/daemon_name: /usr/sbin/gdm3
Jeremy Bicha
<adr...@mx.aik.onl> wrote:
> GDM3 fails to load, after bringing up the system.
interesting messages in
journalctl -b
Probably especially messages from gnome-shell or gdm
Thank you,
Jeremy Bicha
Adrian Immanuel Kiess
here the requested output:
For gdm, it reports this:
avril 22 05:04:26 g6.lan.dac org.freedesktop.secrets[12950]:
GNOME_KEYRING_CONTROL=/var/lib/gdm3/.cache/keyring-DNYYK1 avril 22
05:04:40 g6.lan.dac gdm-launch-environment][12595]:
pam_unix(gdm-launch-environment:session): session closed for user
Debian-gdm avril 22 05:04:40 g6.lan.dac systemd[1]:
var-lib-gdm3-.cache-gvfs.mount: Deactivated successfully. avril 22
05:04:40 g6.lan.dac gdm-launch-environment][12595]: GLib-GObject:
g_object_unref: assertion 'G_IS_OBJECT (object)' failed avril 22
05:04:40 g6.lan.dac systemd[1]: var-lib-gdm3-.cache-doc.mount:
Deactivated successfully. avril 22 05:04:40 g6.lan.dac gdm3[12058]:
Gdm: Child process -12600 was already dead. avril 22 05:04:40
g6.lan.dac systemd[1]: gdm.service: Deactivated successfully.
where it says:
Gdm: Child process -12600 was already dead. avril 22 05:04:40
And for gnome-shell, I found this output:
avril 22 05:04:14 g6.lan.dac gnome-shell[12614]: Error looking up
permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry
for geolocation avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed
to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers
failed: Invalid argument avril 22 05:04:15 g6.lan.dac
gnome-shell[12614]: JS ERROR: Exception in callback for signal:
login-format-changed: Error: Wrong type number; string expected avril
22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: ATK Bridge is disabled
but a11y has already been enabled. avril 22 05:04:15 g6.lan.dac
gnome-shell[12614]: Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Registering session with GDM avril 22
05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:15
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to lock front
buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid
argument avril 22 05:04:15 g6.lan.dac gnome-shell[12614]: Failed to
lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed:
Invalid argument avril 22 05:04:16 g6.lan.dac gnome-shell[12614]:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument avril 22 05:04:16
g6.lan.dac gnome-shell[12614]: Failed to lock front buffer
on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument
avril 22 05:04:20 g6.lan.dac gnome-shell[12614]: No permission to
control network connections: Polkit.Error:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action
org.freedesktop.NetworkManager.network-control is not registered
Where it says:
Failed to lock front buffer on /dev/dri/card0:
drmModeAddFB2WithModifiers failed: Invalid argument
I'd like to note, the recent upgrade has introduced some bugs also with
goa-daemon, where goa-daemon is consistently respawning, after logging
into a X session with startx. If I kill goa-daemon with $ killall -9
goa-daemon, this stops, and I can use my GNOME applications again,
without waiting a half minute for them to start.
Thank you very much.
Sincerely,
Adrian Kiess
Adrian Kieß
after a new gnome-shell package went into Debian/testing, logging in is
possible again. But the load time of GDM3 is still very long, and the
login-procedure takes minutes. After entering the credentials, GDM is
thinking very long and does nothing, then the login proceeds.
Also the login in the shell, when issuing ksu to login to root via
kererberos takes some seconds long. So it might be a bug in conjunction
with the authentification too.
In addition to that, I am currently experiencing a bug in the 5.17
kernel from Debian/testing, where after some hours of uptime one core
gets loaded fully with a kernel process.
In the 5.16 and 5.17 kernels the load time of the ZSH shell is very
slow (may be disk access), so I am currently using an old 5.15 kernel.
My system:
adrian@g6 ~ % inxi
CPU: quad core Intel Xeon X3430 (-MCP-) speed/min/max: 2085/1197/2394
MHz Kernel: 5.15.0-2-amd64 x86_64 Up: 4h 17m Mem: 10022.3/15999.3 MiB
(62.6%) Storage: 11.79 TiB (49.1% used) Procs: 387 Shell: Zsh inxi:
3.3.15
Thank you very much for your attention.
Sincerely,
Adrian Kieß
Adrian Kieß
logging in, into GDM3 is still very slow — the load time of GDM3 is
slow, and the log-in process is slow.
Below is the log of GDM3 from journalctl.
# journalctl -u gdm
mai 30 10:20:01 g6.lan.dac gdm3[3061]: Gdm: GdmDisplay: Session never registered, failing
mai 30 10:20:01 g6.lan.dac gdm3[3061]: Gdm: Child process -49629 was already dead.
mai 30 10:20:03 g6.lan.dac gdm-launch-environment][49725]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=113) by (uid=0)
mai 30 10:39:38 g6.lan.dac gdm3[3061]: Gdm: Child process -49735 was already dead.
mai 30 12:48:04 g6.lan.dac systemd[1]: Stopping GNOME Display Manager...
mai 30 12:48:05 g6.lan.dac gdm3[3061]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
mai 30 12:48:05 g6.lan.dac systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
mai 30 12:48:05 g6.lan.dac systemd[1]: gdm.service: Failed with result 'exit-code'.
mai 30 12:48:05 g6.lan.dac systemd[1]: Stopped GNOME Display Manager.
mai 30 12:48:05 g6.lan.dac systemd[1]: gdm.service: Triggering OnFailure= dependencies.
mai 30 12:48:05 g6.lan.dac systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
-- Boot 3734e8c1a2054aeb818c90aca848b28c --
mai 30 12:49:43 g6.lan.dac systemd[1]: Starting GNOME Display Manager...
mai 30 12:49:43 g6.lan.dac systemd[1]: Started GNOME Display Manager.
mai 30 12:49:44 g6.lan.dac gdm-launch-environment][3190]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=113) by (uid=0)
mai 30 12:50:57 g6.lan.dac gdm-password][4385]: pam_krb5(gdm-password:auth): user adrian authenticated as adr...@LAN.DAC
mai 30 12:50:57 g6.lan.dac gdm-password][4385]: gkr-pam: unable to locate daemon control file
mai 30 12:50:57 g6.lan.dac gdm-password][4385]: gkr-pam: stashed password to try later in open session
mai 30 12:51:35 g6.lan.dac gdm-password][4385]: pam_unix(gdm-password:session): session opened for user adrian(uid=10000) by (uid=0)
mai 30 14:19:46 g6.lan.dac systemd[1]: Stopping GNOME Display Manager...
mai 30 14:19:46 g6.lan.dac gdm3[3148]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
mai 30 14:19:46 g6.lan.dac systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
mai 30 14:19:46 g6.lan.dac systemd[1]: gdm.service: Failed with result 'exit-code'.
mai 30 14:19:46 g6.lan.dac systemd[1]: Stopped GNOME Display Manager.
mai 30 14:19:46 g6.lan.dac systemd[1]: gdm.service: Triggering OnFailure= dependencies.
mai 30 14:19:46 g6.lan.dac systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
-- Boot 736b59854f064875b77021b027c5d600 --
mai 30 14:23:20 g6.lan.dac systemd[1]: Starting GNOME Display Manager...
mai 30 14:23:21 g6.lan.dac systemd[1]: Started GNOME Display Manager.
mai 30 14:23:26 g6.lan.dac gdm-launch-environment][3056]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=113) by (uid=0)
mai 30 14:24:38 g6.lan.dac gdm-password][4306]: pam_krb5(gdm-password:auth): user adrian authenticated as adr...@LAN.DAC
mai 30 14:24:38 g6.lan.dac gdm-password][4306]: gkr-pam: unable to locate daemon control file
mai 30 14:24:38 g6.lan.dac gdm-password][4306]: gkr-pam: stashed password to try later in open session
mai 30 14:25:20 g6.lan.dac gdm-password][4306]: pam_unix(gdm-password:session): session opened for user adrian(uid=10000) by (uid=0)
juin 02 05:49:54 g6.lan.dac gdm3[3039]: GLib: Source ID 79 was not found when attempting to remove it
juin 04 11:32:46 g6.lan.dac gdm3[3039]: GLib: Source ID 86 was not found when attempting to remove it
juin 04 11:32:46 g6.lan.dac systemd[1]: gdm.service: Unexpected error response from GetNameOwner(): Connection terminated
juin 04 11:32:51 g6.lan.dac gdm3[3039]: Gdm: GdmCommon: process (pid:4306, command 'gdm-session-worker [pam/gdm-password]') isn't dying after 5 seconds, now ignoring it.
juin 04 11:32:51 g6.lan.dac systemd[1]: gdm.service: Deactivated successfully.
juin 04 11:32:52 g6.lan.dac systemd[1]: gdm.service: Scheduled restart job, restart counter is at 1.
juin 04 11:32:52 g6.lan.dac systemd[1]: Stopped GNOME Display Manager.
juin 04 11:32:52 g6.lan.dac systemd[1]: Starting GNOME Display Manager...
juin 04 11:33:48 g6.lan.dac systemd[1]: Started GNOME Display Manager.
juin 04 11:33:50 g6.lan.dac gdm-launch-environment][3153266]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=113) by (uid=0)
juin 04 11:34:21 g6.lan.dac gdm-password][3153719]: pam_krb5(gdm-password:auth): user adrian authenticated as adr...@LAN.DAC
juin 04 11:34:21 g6.lan.dac gdm-password][3153719]: gkr-pam: unable to locate daemon control file
juin 04 11:34:21 g6.lan.dac gdm-password][3153719]: gkr-pam: stashed password to try later in open session
juin 04 11:34:36 g6.lan.dac gdm-password][3153719]: pam_unix(gdm-password:session): session opened for user adrian(uid=10000) by (uid=0)
juin 04 11:34:36 g6.lan.dac gdm-password][3153719]: gkr-pam: unlocked login keyring
juin 04 11:34:52 g6.lan.dac gdm3[3153248]: Gdm: Child process -3153337 was already dead.
juin 07 06:34:55 g6.lan.dac systemd[1]: Stopping GNOME Display Manager...
juin 07 06:34:56 g6.lan.dac gdm3[3153248]: Gdm: Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting >
juin 07 06:34:56 g6.lan.dac systemd[1]: gdm.service: Main process exited, code=exited, status=1/FAILURE
juin 07 06:34:56 g6.lan.dac systemd[1]: gdm.service: Failed with result 'exit-code'.
juin 07 06:34:56 g6.lan.dac systemd[1]: Stopped GNOME Display Manager.
juin 07 06:34:56 g6.lan.dac systemd[1]: gdm.service: Triggering OnFailure= dependencies.
juin 07 06:34:56 g6.lan.dac systemd[1]: gdm.service: Failed to enqueue OnFailure= job, ignoring: Unit plymouth-quit.service not found.
-- Boot 313184ca87c74edca1327de4b4b6dd85 --
juin 07 09:04:26 g6.lan.dac systemd[1]: Starting GNOME Display Manager...
juin 07 09:04:26 g6.lan.dac systemd[1]: Started GNOME Display Manager.
juin 07 09:04:26 g6.lan.dac gdm-launch-environment][3281]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=113) by (uid=0)
juin 07 09:05:34 g6.lan.dac gdm-password][4379]: pam_krb5(gdm-password:auth): user adrian authenticated as adr...@LAN.DAC
juin 07 09:05:34 g6.lan.dac gdm-password][4379]: gkr-pam: unable to locate daemon control file
juin 07 09:05:34 g6.lan.dac gdm-password][4379]: gkr-pam: stashed password to try later in open session
juin 07 09:06:10 g6.lan.dac gdm-password][4379]: pam_unix(gdm-password:session): session opened for user adrian(uid=10000) by (uid=0)
An noticeable error might be this message in conjunction with the accountsservice:
Failed to contact accountsservice: Error calling StartServiceByName for org.freedesktop.Accounts: Refusing activation, D-Bus is shutting down.
Thank you very much in advance.
With best greetings from Leipzig, Germany.
Adrian Kieß
today I could fix the slow login process of GDM3 on my Debian system.
This is my coreutils bugreport:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013260
Hello Michael,
after a reboot and looking again at the strace output I disabled the
nmbd, smbd and winbind service which made the bug dissapear.
In summary, I installed nscd which was missing on my system and
disabled the three Samba services above, which I don't need currently.
Everything now works fine again!
This also fixed my slow GDM3 login problem.
Thank you a lot!
-------------
Now my GDM3 login works fine again!
Thanks a lot!
You can close this bug.
With many greetings,
Adrian Kieß