Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47106 - [pam] Last pam update (1.2.1-3) breaks systemd on boot.
Attached to Project:
Arch Linux
Opened by Alexandre Garnier (agarnier) - Wednesday, 18 November 2015, 09:19 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 30 November 2015, 10:16 GMT
Opened by Alexandre Garnier (agarnier) - Wednesday, 18 November 2015, 09:19 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 30 November 2015, 10:16 GMT
|
DetailsDescription:
After last update of pam, several systemd services fail on startup, stopping the boot process (other TTYs remain accessible though, allowing the user to downgrade the package). Additional info: * package version(s): 1.2.1-3 (1.2.1-2 worked before update, and works again after downgrade). * failed services, from journalctl trace: -- Logs begin at ven. 2014-04-11 13:26:27 CEST, end at mar. 2015-11-17 11:45:31 CET. -- nov. 17 11:16:44 ************ systemd[1]: Failed to start Login Service. nov. 17 11:18:15 ************ systemd[1]: Failed to start Accounts Service. nov. 17 11:18:16 ************ systemd[1]: Failed to start Authorization Manager. nov. 17 11:18:18 ************ systemd[1]: Failed to start WPA supplicant. nov. 17 11:18:19 ************ systemd[1]: Failed to start Manage, Install and Generate Color Profiles. nov. 17 11:18:21 ************ systemd[1]: Failed to start Network Manager Script Dispatcher Service. Steps to reproduce: 1. Update pam to 1.2.1-3; 2. Reboot. |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Monday, 30 November 2015, 10:16 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 227 regression, fixed in systemd 228; somehow trigged by the pam_limits changes.
Monday, 30 November 2015, 10:16 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 227 regression, fixed in systemd 228; somehow trigged by the pam_limits changes.
Yes.
“Does the journal contain any clues (error messages) as to why those services fail to start?”
In the attached file are listed some error messages from journalctl linked to the failed services.
I noticed this line especially which might be directly linked to the default TTY being stuck with a failed systemd boot (as it is configured to launch a gdm session):
nov. 17 11:17:17 ************ gdm-launch-environment][693]: pam_systemd(gdm-launch-environment:session): Failed to create session: Connexion terminée par expiration du délai d'attente
It also seems that I encountered two similar errors for the two sessions I opened in console TTYs, which took some time to open, but didn’t failed at it though:
nov. 17 11:20:08 ************ login[877]: pam_systemd(login:session): Failed to create session: Connection timed out
nov. 17 11:24:58 ************ login[890]: pam_systemd(login:session): Failed to create session: Connection timed out
P.S.: « Connexion terminée par expiration du délai d'attente » seems to be the french translation (a side effect of Gnome localization I guess) for “Connection timed out”, FYI.
(The error messages seem completely unrelated to the changes in pam 1.2.1-3; even though a pam downgrade fixes it, I believe the issue lies elsewhere.)
I just did it (downgrading systemd only to 226-3, and re-updating pam to 1.2.1-3) and it works, for now (as an occasional fail on boot is mentioned, I’ll see in the next couple of days if it’s consistent).
I’ll wait for the 228 version to come to the core repo before requesting closure then, unless you close the task before.
Thank you again, I’m requesting closure of this task.