unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: Rutherther <rutherther@ditigal.xyz>, help-guix <help-guix@gnu.org>
Subject: Re: Auto login stopped working
Date: Tue, 05 Nov 2024 23:50:06 +0000	[thread overview]
Message-ID: <87ldxxfdg1.fsf@posteo.net> (raw)
In-Reply-To: <875xp1r2zf.fsf@ditigal.xyz>

Hi,

Rutherther <rutherther@ditigal.xyz> writes:

>> elogind and dbus-system is running, and it works fine if I manually
>> login on another tty, tty3 just shows the `Error in service module`
>> message.  Anyone know what could be the issue?
>
> Hello Fredrik,
>
> I don't know what the cause is, but I was able to get around it
> by setting (login-pause? #t). This means I have to hit enter to log in,
> but I personally actually prefer that. If this is not for you, I don't have
> any more pointers unfortunately.

That might be a good clue, as 

Felix Lechner <felix.lechner@lease-up.com> writes:

> Based on the log messages, it seems pam_elogind.so cannot connect to
> Dbus ("No such file or directory") and leaves the authentication token
> uninitialized, which causes an error in pam_unix.so.

So it sounds like it's failing to login due to dbus is not there.  I can
login normally with that user on a different tty and you — Rutherther —
can login if pausing the login.  Which means that dbus should be there
by then.  I wonder if there is a race condition and it is trying to
login before everything is setup, which would explain why it works when
pausing the login.

I'll do some investigation this weekend to see if I can get any the
wiser on what's going on.  And good to know that there is a workaround
with (login-pause? #t).

Thanks!

-- 
s/Fred[re]+i[ck]+/Fredrik/g


      reply	other threads:[~2024-11-05 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-04  4:29 Auto login stopped working Fredrik Salomonsson
2024-11-05 17:43 ` Rutherther
2024-11-05 23:50   ` Fredrik Salomonsson [this message]

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=87ldxxfdg1.fsf@posteo.net \
    --to=plattfot@posteo.net \
    --cc=help-guix@gnu.org \
    --cc=rutherther@ditigal.xyz \
    /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.
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).