emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#52051: closed ([core-updates-frozen] cannot login ('org.freedesktop.


From: GNU bug Tracking System
Subject: bug#52051: closed ([core-updates-frozen] cannot login ('org.freedesktop.login1' service times out))
Date: Wed, 22 Dec 2021 23:39:01 +0000

Your message dated Wed, 22 Dec 2021 18:38:26 -0500
with message-id <YcO28rn9HnZBLxwQ@jasmine.lan>
and subject line Re: bug#52051: [core-updates-frozen] cannot login 
('org.freedesktop.login1' service times out)
has caused the debbugs.gnu.org bug report #52051,
regarding [core-updates-frozen] cannot login ('org.freedesktop.login1' service 
times out)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
52051: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52051
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Date: Tue, 23 Nov 2021 01:47:07 -0500
Hello,

I'm not 100% sure this is the cause, but these are the last messages I
have before I rebooted:

--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.

Thanks,

Maxim



--- End Message ---
--- Begin Message --- Subject: Re: bug#52051: [core-updates-frozen] cannot login ('org.freedesktop.login1' service times out) Date: Wed, 22 Dec 2021 18:38:26 -0500
On Wed, Dec 22, 2021 at 04:16:30PM -0500, Leo Famulari wrote:
> On Tue, Dec 21, 2021 at 09:19:20PM -0500, Leo Famulari wrote:
> > Would someone like to write a proper commit message and add a code
> > comment?
> 
> How about the attached patch? I'd like to push this soon, because it's a
> severe problem for some users.

> From ab9c4de76dea889e5d05bcf7fa173868357d5f44 Mon Sep 17 00:00:00 2001
> From: Timothy Sample <samplet@ngyro.com>
> Date: Tue, 21 Dec 2021 11:52:34 -0500
> Subject: [PATCH] services: dbus: Wait 1 minute for elogind to get ready.
> 
> Fixes <https://issues.guix.gnu.org/issue/52051>.
> 
> * gnu/services/dbus.scm (dbus-configuration-directory): Set a 60 second 
> timeout
> in the dbus config.

Pushed as 488f1c589df00e802163af534294d93372e5c025

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]