[Bug 786221] Re: Dbus fails to (re)start if `/var/run/dbus/` is present

[Ivan Angelov]

While the patch in comment #2 is a workaround for the dbus daemon, it
does not solve the underlying problem, which seems to be caused by the
migration from /var/run, /var/lock and /dev/shm to /run, /run/lock and
/run/shm, respectively. (Check out the OneiricOcelot release notes here
--
https://wiki.ubuntu.com/OneiricOcelot/ReleaseNotes?action=show&redirect=OneiricOcelot%2FTechnicalOverview.)

Moving the contents of /var/run and /var/lock to /run and /run/lock and
symlinking /var/run -> /run and /var/lock -> /run/lock, as suggested in
comment #40 to bug #856810 seems to fix the problem (along with a bunch
of other problems). Thus, the patch in comment #2 is not necessary.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/786221

Title:
  Dbus fails to (re)start if `/var/run/dbus/` is present

Status in “dbus” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: dbus

  After stopping dbus with `sudo stop dbus`, the directory
  `/var/run/dbus` and its contents are still present. The next time DBus
  is started using `sudo start dbus`, the pid file (and socket?) is
  outdated. This causes issues with NetworkManager.

  Version:
  Kubuntu 11.04 Natty 64 bits installed from Kubuntu 11.04 Natty Alternate CD
  0.8.4~git.20110319t175609.d14809b-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/786221/+subscriptions