dbus exception when running under schroot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Image Tools |
Fix Released
|
High
|
Guilherme Salgado |
Bug Description
I would like to run l-m-c to create images under schroot so that sudo/root permission is not needed. This is so that we can extract boot/rootfs filesystems from the image for use in the validation farm. However, it seems that there are problems trying to run it under schroot:
Setting up linux-image-
Running depmod.
update-initramfs: Generating /boot/initrd.
/bin/df: Warning: cannot read table of mounted file systems: No such file or directory
Examining /etc/kernel/
run-parts: executing /etc/kernel/
Setting up devio (1.2-1build1) ...
Setting up flash-kernel (2.28ubuntu12) ...
Setting up linux-firmware (1.45) ...
Setting up linux-image-
Setting up u-boot-
Setting up u-boot-tools (2010.12-1ubuntu2) ...
Setting up uboot-mkimage (2010.12-1ubuntu2) ...
Setting up x-loader-omap (1.4.4git201007
Done
Cleaning up ...Done
-------
proc umounted
Warning: beagle-
Disk beagle-
sfdisk: ERROR: sector 0 does not have an msdos signature
beagle-
No partitions found
BLKRRPART: Inappropriate ioctl for device
If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)
to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)
Formating boot partition
Traceback (most recent call last):
File "./linaro-
args.
File "/home/
ensure_
File "/home/
if is_partition_
File "/home/
device_path = _get_udisks_
File "/home/
bus = dbus.SystemBus()
File "/usr/lib/
private=
File "/usr/lib/
bus = BusConnection.
File "/usr/lib/
bus = cls._new_
dbus.exceptions
Related branches
Changed in linaro-image-tools: | |
importance: | Undecided → High |
assignee: | nobody → Guilherme Salgado (salgado) |
Changed in linaro-image-tools: | |
importance: | Medium → High |
Changed in linaro-image-tools: | |
status: | Triaged → Fix Committed |
Changed in linaro-image-tools: | |
status: | Fix Committed → Fix Released |
Paul, can you try bind mounting the system's /var/run/dbus into <chroot> /var/run/ dbus and running l-m-c again? That should workaround this issue. (got this idea from http:// lists.freedeskt op.org/ archives/ hal/2008- October/ 012380. html)
A proper fix might involve switching from UDisks to running fdisk and/or other commands directly and parsing their output, which is far from optimal so it'd be great if we could find an acceptable way to workaround this on chroots.