unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Fredrik Salomonsson <plattfot@posteo.net>
To: help-guix <help-guix@gnu.org>
Subject: Auto login stopped working
Date: Mon, 04 Nov 2024 04:29:43 +0000	[thread overview]
Message-ID: <87msifpqo8.fsf@posteo.net> (raw)

Hi Guix,

A few weeks back the auto-login for my media machine stopped working.  I
can still login fine with the user — `htpc`.  I've been scratching my
head on what could be the issue.  I followed the suggestion in the cookbook:

```
;; From cookbook [0]
;; [0] https://guix.gnu.org/cookbook/en/html_node/Auto_002dLogin-to-a-Specific-TTY.html
(define (auto-login-to-tty config tty user)
  (if (string=? tty (mingetty-configuration-tty config))
        (mingetty-configuration
         (inherit config)
         (auto-login user))
        config))

 (modify-services
          %plt-base-services
        (mingetty-service-type
         config => (auto-login-to-tty
                    config "tty3" "htpc")))
```

Checking the `/var/log/secure` all I see is:

```
Nov  2 13:03:16 localhost login[269]: pam_elogind(login:session): Failed to connect to system bus: No such file or directory
Nov  2 13:03:16 localhost login[269]: pam_unix(login:session): session opened for user htpc(uid=1010) by LOGIN(uid=0)
Nov  2 13:03:16 localhost login[269]: Error in service module
```

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?

Thanks

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


             reply	other threads:[~2024-11-04  4:30 UTC|newest]

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

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