touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Public bug reported:

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

** Affects: dbus (Ubuntu)
     Importance: High
     Assignee: Martin Pitt (pitti)
         Status: Triaged


** Tags: systemd-boot

** Tags added: systemd-boot

** Changed in: dbus (Ubuntu)
       Status: New => Triaged

** Changed in: dbus (Ubuntu)
   Importance: Undecided => High

** Changed in: dbus (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Summary changed:

- stops too early under systemd
+ D-Bus stops too early under systemd

-- 
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:
  D-Bus stops too early under systemd

Status in dbus package in Ubuntu:
  Triaged

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/ubuntu/+source/dbus/+bug/1438612/+subscriptions