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
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

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.
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).

Loading...