Bug #8046
Tails Installer crashes on Jessie
0%
Description
Steps to reproduce:
- Copy the ISO manually on a USB stick
- Open a terminal
- Execute liveusb-creator-launcher
Traceback:
[creator:1200] extlinux not found! Only FAT filesystems will be supported
Traceback (most recent call last):
File “/usr/bin/liveusb-creator”, line 99, in
main()
File “/usr/bin/liveusb-creator”, line 94, in main
LiveUSBApp(opts, sys.argv)
File “/usr/lib/python2.7/dist-packages/liveusb/gui.py”, line 64, in init
self.mywindow = LiveUSBDialog(opts, args)
File “/usr/lib/python2.7/dist-packages/liveusb/gui.py”, line 335, in init
self.live = LiveUSBCreator(opts=opts)
File “/usr/lib/python2.7/dist-packages/liveusb/creator.py”, line 625, in init
“/org/freedesktop/UDisks”)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
File “/usr/lib/python2.7/dist-packages/dbus/proxies.py”, line 248, in init
self._named_service = conn.activate_name_owner(bus_name)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 180, in activate_name_owner
self.start_service_by_name(bus_name)
File “/usr/lib/python2.7/dist-packages/dbus/bus.py”, line 278, in start_service_by_name
‘su’, (bus_name, flags)))
File “/usr/lib/python2.7/dist-packages/dbus/connection.py”, line 651, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UDisks was not provided by any .service files
Subtasks
History
#1 Updated by intrigeri 2014-10-10 01:09:21
Building an ISO with the udisks package installed might be enough. If not, then we’ll probably have to port Tails Installer to UDisks2.
#2 Updated by intrigeri 2014-11-17 10:56:04
- Category set to Installation
Installing the udisks package triggers the emergency shutdown (so, in the current state of things, one is logged out: Bug #8098) but then one can successfully start Tails Installer. So, it might be that we can avoid porting Tails Installer to UDisks2 for the time being.
However, a USB drive plugged into the system isn’t seen as a valid candidate target: [creator:712] Unable to write on /dev/sdb, skipping. so it’s not added to the list of devices in the GUI. And indeed:
brw-rw---- 1 root disk 8, 16 Nov 17 10:43 /dev/sdbliveusb-creator upstream doesn’t seem to have any fix for that, but they recommend running as root, so we shouldn’t hold our breath. We could delegate the operations that need write access to the raw block device to privileged helpers.
#3 Updated by anonym 2014-11-18 17:40:30
- Status changed from Confirmed to Resolved
- Feature Branch set to feature/jessie
intrigeri wrote:
> Installing the udisks package triggers the emergency shutdown (so, in the current state of things, one is logged out: Bug #8098) but then one can successfully start Tails Installer. So, it might be that we can avoid porting Tails Installer to UDisks2 for the time being.
I think so. I added udisks to config/chroot_local-packageslists/tails-common.list (commit c06b47e) and built an image, and it starts…
> However, a USB drive plugged into the system isn’t seen as a valid candidate target: [creator:712] Unable to write on /dev/sdb, skipping. so it’s not added to the list of devices in the GUI. And indeed:
>
> […]
>
> liveusb-creator upstream doesn’t seem to have any fix for that, but they recommend running as root, so we shouldn’t hold our breath. We could delegate the operations that need write access to the raw block device to privileged helpers.
… and I get this issue, now is tracked separately in Bug #8273.
#4 Updated by intrigeri 2014-11-23 17:16:30
- related to
Feature #8290: Port Tails Installer to UDisks2 added
#5 Updated by intrigeri 2015-07-08 08:15:25
- related to deleted (
Feature #8290: Port Tails Installer to UDisks2