From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 52051@debbugs.gnu.org
Subject: bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out)
Date: Thu, 25 Nov 2021 23:13:42 +0100 [thread overview]
Message-ID: <87sfvjdgtl.fsf@gnu.org> (raw)
In-Reply-To: <87sfvlos26.fsf@gmail.com> (Maxim Cournoyer's message of "Wed, 24 Nov 2021 22:03:13 -0500")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Nov 24 21:23:58 localhost dbus-daemon[341]: [system] Activating service name='org.freedesktop.login1' requested by ':1.16' (uid=0 pid=324 comm="/gnu/store/ximad0zvg12r4x0x80mvym8hzg0n33jl-shadow") (using servicehelper)
> Nov 24 21:23:58 localhost elogind[1114]: elogind is already running as PID 355
> Nov 24 21:24:11 localhost wpa_supplicant[343]: wlp4s0: CTRL-EVENT-BEACON-LOSS
> Nov 24 21:24:21 localhost last message repeated 5 times
> Nov 24 21:24:23 localhost dbus-daemon[341]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
> Nov 24 21:24:23 localhost shepherd[1]: Respawning term-tty2.
> Nov 24 21:24:23 localhost shepherd[1]: Service host-name has been started.
> Nov 24 21:24:23 localhost shepherd[1]: Service term-tty2 has been started.
> Nov 24 21:24:23 localhost wpa_supplicant[343]: wlp4s0: CTRL-EVENT-BEACON-LOSS
> Nov 24 21:24:27 localhost last message repeated 3 times
> Nov 24 21:26:04 localhost dbus-daemon[341]: [system] Activating service name='org.freedesktop.login1' requested by ':1.17' (uid=0 pid=429 comm="/gnu/store/nvvmksc9pvahqmypaz3h8mqya82vnga8-slim-1") (using servicehelper)
> Nov 24 21:26:04 localhost elogind[1127]: elogind is already running as PID 355
> Nov 24 21:26:29 localhost dbus-daemon[341]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
It looks like elogind things it’s already running as PID 355, where the
PID comes from its PID file; there’s indeed a process with this PID, but
is it really elogind? Or could it be that there’s a stale PID file?
Does /var/log/messages shows the very first time elogind is started at
boot time? With which PID?
We need to find out why dbus-daemon thinks it needs to restart elogind.
Ludo’.
next prev parent reply other threads:[~2021-11-25 22:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 6:47 bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Maxim Cournoyer
2021-11-24 9:02 ` Josselin Poiret via Bug reports for GNU Guix
2021-11-25 3:03 ` Maxim Cournoyer
2021-11-25 22:13 ` Ludovic Courtès [this message]
2021-11-25 4:07 ` Maxim Cournoyer
2021-11-25 22:07 ` Maxim Cournoyer
2021-11-26 9:35 ` Josselin Poiret via Bug reports for GNU Guix
2021-12-07 21:23 ` Maxim Cournoyer
2021-12-07 22:15 ` Maxim Cournoyer
2021-12-08 22:18 ` Ludovic Courtès
2021-12-09 14:18 ` Maxim Cournoyer
2021-12-09 22:15 ` Ludovic Courtès
2021-12-10 5:09 ` Maxim Cournoyer
2021-12-10 10:17 ` Ludovic Courtès
2021-12-16 18:24 ` Josselin Poiret via Bug reports for GNU Guix
2021-12-21 9:31 ` Timothy Sample
2021-12-21 16:13 ` Leo Famulari
2021-12-21 16:36 ` Timothy Sample
2021-12-21 16:52 ` Maxime Devos
2021-12-21 17:32 ` Leo Famulari
2021-12-21 17:51 ` Maxime Devos
2021-12-21 18:11 ` Leo Famulari
2021-12-21 17:37 ` Leo Famulari
2021-12-21 17:44 ` Leo Famulari
2021-12-08 2:12 ` Maxim Cournoyer
2021-12-15 19:27 ` Michael Rohleder
2021-12-16 3:36 ` Abhiseck Paira via Bug reports for GNU Guix
2021-12-16 13:09 ` ison
2021-12-16 17:59 ` bug#52051: [core-updates-frozen] cannot login Guillaume Le Vaillant
2021-12-16 18:53 ` bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Michael Rohleder
2021-12-20 0:40 ` Caleb Herbert
2021-12-22 1:46 ` Luis Felipe via Bug reports for GNU Guix
2021-12-22 2:19 ` Leo Famulari
2021-12-22 21:16 ` Leo Famulari
2021-12-22 23:38 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfvjdgtl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=52051@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.