The title of this bug is a little confusing, I am trying to deal with this bug and I almost filed a separate bug with this description:
"Upgrades of the dbus package fail unless dbus is running" This is a problem for a number of reasons: 1. if you are running in a chroot, dbus upgrades fail. I imagine this is a problem in other similar installation or maintenance scenarios, including the uck package (Ubuntu Customization Kit) 2. if somehow dbus got broken and couldn't start, you could never reinstall or upgrade it to fix the problem This can sometimes be worked around by binding /var/run/dbus on the host system, but what is the upgrade doing over the bus that should really be happening to the chroot system? If it is nothing important the package should not die on the error, and if it is important then the package should be updated to store the necessary bus commands and run them the next time the bus is active. This was a somewhat smaller problem in Jaunty and earlier Ubuntu releases that could easily be worked around by explicitly starting dbus in the chroot, but now with recent init script updates it detects the dbus process from the host system and won't "start" in the chroot. This issue needs to be formally addressed. error log: Setting up dbus (1.2.16-0ubuntu9) ... Installing new version of config file /etc/dbus-1/system.conf ... The system user `messagebus' already exists. Exiting. Failed to open connection to "system" message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory dpkg: error processing dbus (--configure): -- within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) https://bugs.launchpad.net/bugs/441100 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
