[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1'
From: |
Josselin Poiret |
Subject: |
bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) |
Date: |
Wed, 24 Nov 2021 09:02:16 +0000 |
Hello Maxim,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> --8<---------------cut here---------------start------------->8---
> 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)
> --8<---------------cut here---------------end--------------->8---
>
> 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.
I cannot reproduce in a fresh VM on commit
d5de4e163ccef80f78bc5fe330f568d8fe3a23ab, and can login just fine, with
(services (cons* (service slim-service-type (slim-configuration))
(modify-services %desktop-services
(delete gdm-service-type))))
Is this still affecting you?
Best,
Josselin Poiret