From: ludo@gnu.org (Ludovic Courtès)
To: William <w@vieta.uk>
Cc: 27580@debbugs.gnu.org
Subject: bug#27580: Elogin doesn't start properly
Date: Tue, 11 Jul 2017 00:21:37 +0200 [thread overview]
Message-ID: <87bmos2ary.fsf@gnu.org> (raw)
In-Reply-To: <CAPCYgVdLByzKBR0cGQ7f32+U0jCMDH6ZCvJTQB=L1MbNg95j5Q@mail.gmail.com> (William's message of "Wed, 5 Jul 2017 00:39:05 +0100")
Hello,
William <w@vieta.uk> skribis:
> Elogind only starts when loginctl is executed as loginctl activates
> elogind via DBus, meaning that it doesn't record any logins before
> loginctl is run. I don't believe that this is intended; my Arch Linux
> install doesn't miss any logins.
I thought pam_elogind would trigger bus-activation but it does not,
because of this:
/* Make this a NOP on non-logind systems */
if (!logind_running())
return PAM_SUCCESS;
where:
static inline bool logind_running(void) {
return access("/run/systemd/seats/", F_OK) >= 0;
}
When the system is started, /run/systemd is empty, so pam_elogind
directly returns success.
I’m looking for a way to work around this; to be continued…
Ludo’.
PS: The problem does not happen with X and SLiM because they somehow
activate elogind before one has logged in.
next prev parent reply other threads:[~2017-07-10 22:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 23:39 bug#27580: Elogin doesn't start properly William
2017-07-10 22:21 ` Ludovic Courtès [this message]
[not found] ` <CAPCYgVfvS1HoWvb8H1oJM+xCx2P6bUSCOEnSEikpRs47ao8+Hw@mail.gmail.com>
2017-07-11 7:33 ` bug#27580: Fwd: " William
2017-07-11 9:13 ` Ludovic Courtès
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=87bmos2ary.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27580@debbugs.gnu.org \
--cc=w@vieta.uk \
/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).