[Bug 552404] [NEW] dbus fails to be configured in chroots

Launchpad Bug Tracker 552404 at bugs.launchpad.net
Mon Feb 14 09:54:36 UTC 2011


You have been subscribed to a public bug by Alkis Georgopoulos (alkisg):

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.

** Affects: dbus (Ubuntu)
     Importance: Medium
         Status: Confirmed


** Tags: lucid patch
-- 
dbus fails to be configured in chroots
https://bugs.launchpad.net/bugs/552404
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is a direct subscriber.



More information about the Ubuntu-sponsors mailing list