touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #67692
[Bug 1438612]
(In reply to Simon McVittie from comment #6)
> Perhaps it would be better to make the stop command exit
> nonzero?
Straw man:
ExecStop=/bin/sh -c "echo Stopping the system dbus-daemon is not
supported. Reboot the system instead.; exit 1"
... which does work, but logs "Unit dbus.service entered failed state"
during shutdown. It seems better to avoid "crying wolf" if possible,
because it can hide real issues.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1438612
Title:
remote file systems hang on shutdown, D-BUS stops too early
Status in D-Bus:
Confirmed
Status in dbus package in Ubuntu:
Fix Released
Bug description:
(part of bug 1431774). During shutdown, D-Bus stops too early. In
particular, it stops before NetworkManager and remote-fs.target, so
that any network unmount will cause errors and hang the boot. This
can be seen with
$ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)'
Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus...
Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus.
Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems.
Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems.
Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre).
Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre).
Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager...
Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager.
Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket.
A quick workaround is to add After=dbus.service to
/lib/systemd/system/NetworkManager.service's [Unit] section, but this
should be fixed in a more general fashion.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus/+bug/1438612/+subscriptions
References