FS#61321 - Systemd 240 breaks systemd --user autolaunch
Attached to Project:
Arch Linux
Opened by Denis Speranskiy (Speranskiy) - Wednesday, 09 January 2019, 10:48 GMT
Last edited by Jan de Groot (JGC) - Friday, 31 May 2019, 06:41 GMT
Opened by Denis Speranskiy (Speranskiy) - Wednesday, 09 January 2019, 10:48 GMT
Last edited by Jan de Groot (JGC) - Friday, 31 May 2019, 06:41 GMT
|
Details
After upgrade to systemd 240.0-3 it's not possible to get
`systemd --user` being launched on boot neither by linger
nor by a login.
loginctl session-status displays errors: `pam_exec(login:session): conversation failed` Downgrading to systemd 239.370-1 fixes the issue |
This task depends upon
Closed by Jan de Groot (JGC)
Friday, 31 May 2019, 06:41 GMT
Reason for closing: Not a bug
Additional comments about closing: Misconfiguration
Friday, 31 May 2019, 06:41 GMT
Reason for closing: Not a bug
Additional comments about closing: Misconfiguration
Comment by
Dave Reisner (falconindy) -
Wednesday, 09 January 2019, 12:04 GMT
Comment by
Denis Speranskiy (Speranskiy) -
Wednesday, 09 January 2019, 12:27 GMT
Comment by
Dave Reisner (falconindy) - Monday,
21 January 2019, 19:48 GMT
Comment by
Denis Speranskiy (Speranskiy) -
Tuesday, 22 January 2019, 03:10 GMT
Works fine here. There should be more errors than just the PAM
failure in the journal.
I just upgraded back to the latest 240.0-3 and got the same
situation when systemd --user is not being launched. Where to look
for the proper logs?
If you're requesting closure because of a misconfiguration on your
side, what exactly *is* that misconfiguration?
I've added a motd script that had started to fail because of I've
configured a custom local repo so PAM was not able to spawn a user
session and it occured that systemd 240 is sensitive to this sort
of issue for some reason.