GNU bug report logs - #37191
Cannot login after graphical install

Previous Next

Package: guix;

Reported by: Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>

Date: Mon, 26 Aug 2019 14:38:02 UTC

Severity: normal

Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #19 received at 37191-done <at> debbugs.gnu.org (full text, mbox):

From: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>,
 37191-done <at> debbugs.gnu.org
Subject: Re: bug#37191: Cannot login after graphical install
Date: Wed, 28 Sep 2022 22:53:23 -0400
Hi,

Ludovic Courtès <ludo <at> gnu.org> writes:

> Hello,
>
> (Please keep the bug Cc’d.)
>
> Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com> skribis:
>
>>> > Aug 26 15:14:04 localhost login[203]: pam_elogind(login:session):
>>> > Failed to connect to system bus: No such file or directory
>>> > Aug 26 15:14:04 localhost login[203]: pam_unix(login:session):
>>> > session opened for user jussi by LOGIN(uid=0)
>>> > Aug 26 15:14:04 localhost login[203]: Cannot make/remove an entry for the specified session
>>>
>>> It seems that there’s at least one serious problem, which is
>>> /var/run/dbus/system_bus_socket is unavailable, for some reason.
>>>
>>> Did the ‘dbus-system’ shepherd service start correctly, or did you get
>>> messages suggesting otherwise?
>
> [...]
>
>> It failed to start as can be seen from the 'debug' logfile:
>>> Aug 26 01:27:27 localhost shepherd[1]: Service dbus-system could not be started.
>
> Are there additional clues in /var/log/{messages,debug}, or perhaps on
> tty1, as to why dbus failed to start?

Closing, due to lack of requested information.

-- 
Thanks,
Maxim




This bug report was last modified 2 years and 238 days ago.

Previous Next


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