[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
Closing due to age. If a similar problem appears in the latest Ubuntu release please open a new report. ** Changed in: dbus (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441100 Title: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/441100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
On my laptop running natty, with natty schroot, this workaround works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441100 Title: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
grr... sorry, wrong bug. Please ignore previous comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441100 Title: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
I was failing to reinstall a lot of packages (perhaps the problem was in dbus one) and the first suggestion worked for me (not upgrading): mount --bind /var/run/dbus/ chroot/var/run/dbus/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/441100 Title: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
Confirmed, Lucid in chroot: LANG=C sudo apt-get install --reinstall dbus Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 3 not upgraded. 3 not fully installed or removed. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Can not write log, openpty() failed (/dev/pts not mounted?) Setting up dbus (1.2.16-2ubuntu4) ... 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): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of gconf2-common: gconf2-common depends on dbus; however: Package dbus is not configured yet. dpkg: error processing gconf2-common (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of libgconf2-4: libgconf2-4 depends on gconf2-common (= 2.28); however: Package gconf2-common is not configured yet. libgconf2-4 depends on gconf2-common ( 2.29); however: Package gconf2-common is not configured yet. dpkg: error processing libgconf2-4 (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: dbus gconf2-common libgconf2-4 E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
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
[Bug 441100] Re: within chroot, can fail to reload daemon configuration if not running (detects dbus daemon outside of chroot)
How do I fix a schroot, built with mk-sbuild-lv? Logging into it using schroot -c karmic-source -u root shows the bind mount I've applied via into /var/lib/schroot/mount/karmic-*, /var/run/dbus/system_bus_socket is there, but it says: Setting up dbus (1.2.16-0ubuntu8) ... 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: Connection refused -- 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
