Hey Christian,
Christian Kastner [2014-12-28 21:55 +0100]:
Trying to run as a user instance, but $XDG_RUNTIME_DIR is not set.
I assume that this is because common-session also includes
pam_systemd.so, whereas -noninteractive does not, so switching to the
latter drops it from
Hi Martin,
On 2015-01-21 11:35, Martin Pitt wrote:
On both my Debian sid and my Ubuntu system, the only difference
between common-session and common-session-noninteractive is that the
latter does not include libpam-systemd.
Generally speaking, I believe (but haven't verified) that this will
On Mon, 05 Jan 2015 20:57:05 +0100 Christian Kastner deb...@kvr.at wrote:
If this second PAM session via systemd-user is indeed intended to be
merely a background thing, them common-session-noninteractive should be
the way to go anyway. But I'm not familiar enough with systemd to make
that
On 2015-01-20 19:28, Felipe Sateler wrote:
For reference, the inclusion of common-session is a local debian
patch[1]. The original file referenced system-auth, which apparently
debian does not use.
[1]
Control: severity -1 serious
On Sun, 28 Dec 2014 18:29:57 +0100 Christian Kastner deb...@kvr.at wrote:
The question is why the PAM stack is processed twice. Perhaps there is
some way to inhibit the second invocation, although I am not familiar
enough with systemd/logind to know what to
On 2014-12-28 18:29, Christian Kastner wrote:
Changing systemd-user's PAM config to use common-session-noninteractive
resolves the above issue (and actually another, yet unreported, one in
libpam-mount).
Please consider including the attached patch against git master if you
think it is safe
6 matches
Mail list logo
