I had a very similar looking problem, not under chroot, but running over
ssh, on a server. Is this expected to work in that situation? Bug
#1311368
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/10329
Here's how to work around it:
- Back up /sbin/start
- Replace /sbin/start with a script that does nothing,
#!/bin/sh
exit 0
- Make it executable, # chmod +x /sbin/start
- Run the apt update
- (Restore start if desired)
--
You received this bug notification because you are a member of Ubuntu
Bu
Is there a way to work around this bug, to install packages which depend
on dbus, while waiting for a proper fix? (I don't think I even need a
dbus daemon in the chroot, because I have set up bind-mounts for it to
communicate with the main system's dbus and changed the machine_id)
--
You received
i installed quantal core (2012-10-16 ubuntu-core-12.10-core-
amd64.tar.gz) in a chroot, then, installing dbus yields:
Setting up dbus (1.6.4-1ubuntu4) ...
start: Unknown job: dbus
invoke-rc.d: initscript dbus, action "start" failed.
dpkg: error processing dbus (--configure):
subprocess installed
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dbus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032915
Title:
[quan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1032915
Title:
[quantal] dbus: upgrade fails in chroot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug
