From: ison <ison@airmail.cc>
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, 16 Dec 2021 06:09:01 -0700 [thread overview]
Message-ID: <87sfusofjg.fsf@airmail.cc> (raw)
In-Reply-To: <87pmqr1i8k.fsf@gmail.com>
I may have found a clue about what's happening.
After updating I ran into this same issue (I login from TTY), and I see
the same "elogind is already running" error.
However, if I boot into an older generation (before the
core-updates-frozen merge), and then again reboot back into the newest
generation (after core-updates-frozen merge) then I am able to login.
I was able to reproduce those exact steps too. Reboot to new generation,
can't login again. Reboot to old generation, then reboot back to new
generation and I can log in.
Note that even when I'm able to login on the new generation I still see
the "elogind is already running" error printed, but only before the
login prompt shows up, not after.
Also I'm not sure if this matters, but another difference I notice
during the attempts when I can successfully login on the new generation
is that I see Herd restart the `nscd` service.
Perhaps someone else experiencing this issue should try to restart nscd
(via SSH) and see if that works for you.
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> Hello,
>
> I'm not 100% sure this is the cause, but these are the last messages I
> have before I rebooted:
>
> Nov 23 01:09:14 localhost dbus-daemon[383]: [system] Activating service name='org.freedesktop.login1' requested by ':1.17' (uid=0 pid=370
> comm="/gnu/store/ximad0zvg12r4x0x80mvym8hzg0n33jl-shadow") (using servicehelper)
> Nov 23 01:09:14 localhost elogind[1189]: elogind is already running as PID 390
> Nov 23 01:09:20 localhost shepherd[1]: Respawning term-tty1.
> Nov 23 01:09:20 localhost shepherd[1]: Service host-name has been started.
> Nov 23 01:09:20 localhost shepherd[1]: Service term-tty1 has been started.
> Nov 23 01:09:39 localhost dbus-daemon[383]: [system] Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
>
> I don't remember if I saw the slim login screen; but in any case I
> couldn't successfully login even via a ptty.
>
> It may have to do with polkit.
>
> To be investigated.
>
> This happened on a system *not* using gdm (it uses slim) and with
> ratpoison as the WM, on commit f42bc604547d9ee8e35fcd66d5db7786954cfac3
> of the core-updates-frozen branch.
>
> To be investigated.
>
> Thanks,
>
> Maxim
next prev parent reply other threads:[~2021-12-16 13:19 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
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 [this message]
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=87sfusofjg.fsf@airmail.cc \
--to=ison@airmail.cc \
--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.