Arch Linux

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!
Tasklist

FS#75008 - Regression: upgrade from 2022/06/01 to 2022/06/09 makes system unable to initialize properly

Attached to Project: Arch Linux
Opened by Marek Kozlowski (guayaseal) - Thursday, 09 June 2022, 09:42 GMT
Last edited by Antonio Rojas (arojas) - Thursday, 09 June 2022, 09:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrading system to the most recent version (09/06/2022) lightdm freezes during system startup. journalctl shows something like:

"Error getting user list from org.freedesktop.Accounts: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Accounts was not provided by any .service files"

and it is the only message that suggest some error. Both systemctl and systemd-analyze show everything is fine.

I've logged into tty2 and executed:

# systemctl restart lightdm

and I'm able to see the login screen but it freezes after entering the credentials.

I've also tried:

# systemctl restart dbus; systemctl restart lightdm

and have the login screen, I can login but my Xfce sessions seems seriously corrupted and unusable.

Reverting my system back with:

Server = https://archive.archlinux.org/repos/2022/06/01/$repo/os/$arch

in /etc/pacman.conf

solves the problems.

Seems like "aggressive parallelization" of systemd initializes underlying services in an incorrect order. We all love magic of systemd.

Additional info:
* package version(s)
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Antonio Rojas (arojas)
Thursday, 09 June 2022, 09:49 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#75004 

Loading...