GNU bug report logs - #55488
GDM, GNOME: Can't start desktop session after upgrade

Previous Next

Full log

View this message in rfc822 format

From: Ludovic Courtès <ludo <at> gnu.org>
To: Luis Felipe <luis.felipe.la <at> protonmail.com>
Cc: 55488 <at> debbugs.gnu.org
Subject: bug#55488: GDM, GNOME: Can't start desktop session after upgrade
Date: Wed, 01 Jun 2022 21:55:37 +0200

Hi Luis,

The parts related to elogind I see from the log are the following:

--8<---------------cut here---------------start------------->8---
190:May 31 12:23:27 localhost shepherd[1]: Service elogind has been started.
220:May 31 12:23:14 localhost elogind[382]: New seat seat0.
264:May 31 12:23:15 localhost elogind[382]: Watching system buttons on /dev/input/event2 (Power Button)
280:May 31 12:23:16 localhost dbus-daemon[349]: [system] Activating service name='org.freedesktop.login1' requested by ':1.1' (uid=0 pid=383 comm="/gnu/store/qpaw2f734zlsq153fkn5afcv4k4fk63z-upower") (using servicehelper)
343:May 31 12:23:20 localhost elogind[382]: Watching system buttons on /dev/input/event1 (Power Button)
415:May 31 12:23:26 localhost elogind[382]: Watching system buttons on /dev/input/event0 (Sleep Button)
604:May 31 12:23:41 localhost dbus-daemon[349]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
643:May 31 12:23:45 localhost elogind[382]: Watching system buttons on /dev/input/event6 (HUION Huion Tablet_HS611 Consumer Control)
684:May 31 12:23:49 localhost gdm: Gdm: GdmLocalDisplayFactory: Failed to issue method call: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
752:May 31 12:24:18 localhost vmunix: [   17.648359] shepherd[1]: Service file-system-/sys/fs/cgroup/elogind has been started.
959:May 31 12:24:33 localhost elogind[382]: New session c1 of user gdm.
--8<---------------cut here---------------end--------------->8---

So it has to do with elogind taking too long to start.  Same with
polkit:

--8<---------------cut here---------------start------------->8---
854:May 31 12:24:10 localhost polkitd[426]: Started polkitd version 0.120
925:May 31 12:24:31 localhost shepherd[1]: [dbus-daemon] ** (accounts-daemon:421): CRITICAL **: 12:24:28.105: error getting polkit authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
--8<---------------cut here---------------end--------------->8---

Now, something’s wrong with those timestamps, where shepherd’s message,
which came first, has a timestamp in the future.

Could it be <https://issues.guix.gnu.org/55707>?  At boot time, if you
switch to tty12 (by pressing alt-f12) as soon as it’s available, do you
see messages that get printed pretty slowly, like 4–5 lines per second?

Sorry for not having clearer ideas, but maybe we have a lead…

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.