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

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#37191: closed (Cannot login after graphical install)
Date: Thu, 29 Sep 2022 02:54:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Wed, 28 Sep 2022 22:53:23 -0400
with message-id <87wn9mnb6k.fsf <at> gmail.com>
and subject line Re: bug#37191: Cannot login after graphical install
has caused the debbugs.gnu.org bug report #37191,
regarding Cannot login after graphical install
to be marked as done.

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


-- 
37191: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37191
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>
To: "bug-guix <at> gnu.org" <bug-guix <at> gnu.org>
Subject: Cannot login after graphical install
Date: Mon, 26 Aug 2019 13:10:41 +0000

[Message part 3 (text/plain, inline)]

I'm getting a "Cannot make/remove an entry for the specified session" after logging into the installed system, which returns me to the login prompt. The cause seems to be shepherd failing to start dbus, which PAM depends on. System config file and logs as attachments.

[Message part 4 (text/html, inline)]

[config.scm (text/x-scheme, attachment)]

[secure (application/octet-stream, attachment)]

[debug (application/octet-stream, attachment)]

[Message part 8 (message/rfc822, inline)]

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

Previous Next

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