unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 37191@debbugs.gnu.org, Jussi Kuokkanen <jussi.kuokkanen@protonmail.com>
Subject: bug#37191: Cannot login after graphical install
Date: Tue, 03 Sep 2019 14:25:35 +0200	[thread overview]
Message-ID: <87o901va68.fsf@gnu.org> (raw)
In-Reply-To: <VDnf4QqYMPtjLRoGDmWDpIQ32J8kuXCB1_bQQRQvmx9MqNhzWz_HEK1nZQzmCwhjakGvOPCvWc42SAo3k28Coc13aR4iaxrxARHYyIJdhTY=@protonmail.com> (Jussi Kuokkanen via Bug reports for's message of "Mon, 26 Aug 2019 13:10:41 +0000")

Hi Jussi,

Jussi Kuokkanen via Bug reports for GNU Guix <bug-guix@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’.

  reply	other threads:[~2019-09-03 12:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 13:10 bug#37191: Cannot login after graphical install Jussi Kuokkanen via Bug reports for GNU Guix
2019-09-03 12:25 ` Ludovic Courtès [this message]
2019-09-04 12:05   ` Jussi Kuokkanen
2019-09-05  8:15     ` Ludovic Courtès
2022-09-29  2:53       ` Maxim Cournoyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o901va68.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=37191@debbugs.gnu.org \
    --cc=jussi.kuokkanen@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).