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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37191 in the body.
You can then email your comments to 37191 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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 1 (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 2 (text/html, inline)]

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

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

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

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: 37191 <at> debbugs.gnu.org,  Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>
Subject: Re: bug#37191: Cannot login after graphical install
Date: Tue, 03 Sep 2019 14:25:35 +0200

Hi Jussi,

Jussi Kuokkanen via Bug reports for GNU Guix <bug-guix <at> gnu.org> skribis:

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

[...]

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

Thanks,
Ludo’.

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

From: Ludovic Courtès <ludo <at> gnu.org>
To: Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>
Cc: 37191 <at> debbugs.gnu.org
Subject: Re: bug#37191: Cannot login after graphical install
Date: Thu, 05 Sep 2019 10:15:45 +0200

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?

Thanks,
Ludo’.

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

From: Jussi Kuokkanen <jussi.kuokkanen <at> protonmail.com>
To: Ludovic Courtès <ludo <at> gnu.org>
Subject: Re: bug#37191: Cannot login after graphical install
Date: Wed, 04 Sep 2019 12:05:28 +0000

> Hi Jussi,
>
> Jussi Kuokkanen via Bug reports for GNU Guix bug-guix <at> gnu.org skribis:
>
> > 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.
>
> [...]
>
> > 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?
>
> Thanks,
> Ludo’.

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.

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

Previous Next

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