FS#6394 - gnome-volume-manager does not mount luks encrypted USB-stick

Attached to Project: Arch Linux
Opened by Khashayar Naderehvandi (nightfrost) - Sunday, 11 February 2007, 11:37 GMT
Last edited by Roman Kyrylych (Romashka) - Thursday, 15 February 2007, 09:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When inserting a LUKS-encrypted USB stick, gnome-volume-manager properly detects it and asks for the password. After entering the password nothing happens. By using "cryptsetup luksOpen" on the command line, gnome-volume-manager mounts the device. I don't know whether the problem is with gvm, hal or something else.

Here's something that might be related at ubuntu:

https://launchpad.net/ubuntu/+source/udev/+bug/78848
https://blueprints.launchpad.net/ubuntu/+spec/udev-device-mapper
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 15 February 2007, 18:03 GMT
Reason for closing:  Fixed
Additional comments about closing:  Applied the given patch to look in the correct location for cryptsetup.
Comment by Khashayar Naderehvandi (nightfrost) - Sunday, 11 February 2007, 11:48 GMT
The problem seems to be that the hal script looks for cryptsetup in /sbin/cryptsetup, wheras archlinux has it at /usr/sbin/cryptsetup. After creating a symlink at /sbin/cryptsetup, everything works as expected.
Comment by Khashayar Naderehvandi (nightfrost) - Sunday, 11 February 2007, 12:09 GMT
here's a small patch against hal that simply changes the location where hal looks for cryptsetup.
   cryptsetup_path.patch (1.7 KiB)

Loading...