Comment 35 for bug 567899

Revision history for this message
Evan (ev) wrote :

Right. I'm afraid I need to ask for another test run.

Put the following debs on a USB disk:
if you're on 64-bit: https://edge.launchpad.net/~ev/+archive/ppa/+build/1710338
if you're on 32-bit: https://edge.launchpad.net/~ev/+archive/ppa/+build/1710339

When you see the keyboard icon as the CD is booting, press spacebar. This will bring up the advanced boot options screen. Select a language then arrow down to the "Install Ubuntu" option. Press F6, then escape. You should see a line of text. Change "only-ubiquity" to "maybe-ubiquity" and add a space and "break=bottom" after it. Press enter.

The CD will continue booting and you should end up at an "(initramfs)" prompt. Type `chroot root bash`.

Insert the USB disk that you copied the debs onto, mount it (mount /dev/sdb1 /mnt), and install the debs (dpkg -i /mnt/dbus*.deb).

Next, type nano /etc/dbus-1/system.conf. Delete the line that reads "<fork/>", save the file (ctrl-o, enter), and exit (ctrl-x).

Now type nano /etc/init/dbus.conf. Comment out the "expect fork" and "respawn" lines by putting a # character in front of them. Right below them add a line that says "env DBUS_VERBOSE=1". Change the line that reads "exec dbus-daemon --system --fork" to read "exec strace -tt -s 1024 -o/var/log/dbus.log -- dbus-daemon --system >/var/log/dbus-messages.log 2>&1". Save the file (ctrl-o, enter) and exit (ctrl-x).

Now type exit to bring you back to the (initramfs) prompt. Type exit again. The CD will continue booting and should crash at the installer, as it did before. If it does not crash, try again without the strace call. That is, change the line that reads "exec dbus-daemon --system --fork" to "exec dbus-daemon --system >/var/log/dbus-messages.log 2>&1"

Switch to a virtual terminal (ctrl-alt-f2), plug in and mount the USB disk again (sudo mount /dev/sdb1 /mnt), then copy /var/log/dbus.log and /var/log/dbus-messages.log to it.

Unmount the USB disk (sudo umount /mnt) and attach dbus.log and dbus-messages.log to this bug report.

Thanks so much for helping us get to the bottom of this problem!