[Bug 552404] Re: dbus fails to be configured in chroots

[Launchpad Bug Tracker]

This bug was fixed in the package dbus - 1.4.6-1ubuntu3

---------------
dbus (1.4.6-1ubuntu3) natty; urgency=low

  * debian/dbus.postinst: Prevent dbus.postinst from failing in chroots
    (LP: #552404).
 -- Alkis Georgopoulos <alkisg at gmail.com>   Mon, 14 Feb 2011 11:21:53 +0200

** Changed in: dbus (Ubuntu Natty)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/552404

Title:
  dbus fails to be configured in chroots

Status in “dbus” package in Ubuntu:
  Fix Released
Status in “dbus” source package in Lucid:
  Fix Committed
Status in “dbus” source package in Maverick:
  Fix Committed
Status in “dbus” source package in Natty:
  Fix Released

Bug description:
  Binary package hint: dbus

  Similar to #441100, but I'm not sure if it's a duplicate, so I'm
  filing it separately.

  While upgrading my Lucid/i386 chroot, I got this error:
  "Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory"

  The result was that dbus and all of the packages that depend on it
  were left in an unconfigured state, breaking my chroot.

  Looking at dbus.postinst, the problem seems to be this line:
    dbus-send --print-reply --system --type=method_call \
  	--dest=org.freedesktop.DBus \
    / org.freedesktop.DBus.ReloadConfig > /dev/null

  I believe this should either have an "if we_are_not_in_a_chroot" in front of it,
  or an "|| true" at the end of it, as detecting chroots can be difficult.