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#49817 - [systemd] Failed to propagate agent release message: Transport endpoint is not connected
Attached to Project:
Arch Linux
Opened by Pavel (psp) - Thursday, 23 June 2016, 08:59 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 23 June 2016, 10:58 GMT
Opened by Pavel (psp) - Thursday, 23 June 2016, 08:59 GMT
Last edited by Dave Reisner (falconindy) - Thursday, 23 June 2016, 10:58 GMT
|
DetailsDescription:
During the reboot on May 29, shutdown messages were normal as usual (libssystemd version 229-3 according to pacman.log) ... systemd[1]: Stopped Permit User Sessions. systemd[1]: Stopping Permit User Sessions... systemd[1]: Removed slice system-getty.slice. systemd[1]: Started Generate shutdown-ramfs. ... Current reboot (starting June 8), (libssystemd version 230-3 according to pacman.log) systemd[1]: Stopping Permit User Sessions... systemd[1]: Failed to propagate agent release message: Transport endpoint is not connected systemd[1]: Started Generate shutdown-ramfs. It may mean no harm but may indicate disagreements between dbus and systemd. Steps to reproduce: Reboot. |
This task depends upon
Closed by Dave Reisner (falconindy)
Thursday, 23 June 2016, 10:58 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing to do here, and not reproducible on a minimal system.
Thursday, 23 June 2016, 10:58 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing to do here, and not reproducible on a minimal system.
Comment by Dave Reisner (falconindy) -
Thursday, 23 June 2016, 10:57 GMT
It merely means that dbus has shut down. Everything else is shutting down, too, so there's nothing to do here really. To fix this, you need a bus which sticks around during shutdown (kdbus was the original idea, bus1 is the next idea).