--- Begin Message ---
Subject: |
Cannot login after graphical install |
Date: |
Mon, 26 Aug 2019 13:10:41 +0000 |
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.
config.scm
Description: Text Data
secure
Description: Binary data
debug
Description: Binary data
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#37191: Cannot login after graphical install |
Date: |
Wed, 28 Sep 2022 22:53:23 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
Hi,
Ludovic Courtès <ludo@gnu.org> writes:
> Hello,
>
> (Please keep the bug Cc’d.)
>
> Jussi Kuokkanen <jussi.kuokkanen@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
--- End Message ---