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#73397 - [systemd] systemctl status regression, "Failed to dump process list"
Attached to Project:
Arch Linux
Opened by Bronek Kozicki (bronek) - Monday, 17 January 2022, 20:24 GMT
Last edited by Christian Hesse (eworm) - Thursday, 20 January 2022, 12:46 GMT
Opened by Bronek Kozicki (bronek) - Monday, 17 January 2022, 20:24 GMT
Last edited by Christian Hesse (eworm) - Thursday, 20 January 2022, 12:46 GMT
|
DetailsRegression in systemd. The output of systemctl status is only:
# systemctl status Failed to dump process list for 'gdansk.lan.incorrekt.net', ignoring: Operation not supported ● gdansk.lan.incorrekt.net State: running Jobs: 0 queued Failed: 0 units Since: Mon 2022-01-17 07:46:06 GMT; 11h ago CGroup: / There is no other useful output. * package version(s): 250.2-2 * link to upstream bug report: https://github.com/systemd/systemd/issues/22089 * other: Regression when systemd is accessing "machine.slice" which is used by libvirt. * bugfix: Proposed bugfis is at https://github.com/systemd/systemd/pull/22095 Steps to reproduce: 1. Install and start libvirtd 2. Start a virtual machine under libvirt 3. Run "systemctl status" |
This task depends upon
Closed by Christian Hesse (eworm)
Thursday, 20 January 2022, 12:46 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 250.3-1
Thursday, 20 January 2022, 12:46 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 250.3-1
Comment by loqs (loqs) -
Tuesday, 18 January 2022, 23:46 GMT
Please try systemd 250.3-1 currently in testing which includes the fix.
Comment by Bronek Kozicki (bronek) -
Thursday, 20 January 2022, 09:25 GMT
Thank you, that fixes it - this ticket can be closed now!