[Pkg-utopia-maintainers] Re: Is it a bug?

[Michael Biebl]

Magnus Therning wrote:
> On Fri, Apr 20, 2007 at 01:49:01 +0200, Michael Biebl wrote:
>> Magnus Therning wrote:
>>> I thought I'd check before raising this as a bug:
>>> http://lists.debian.org/debian-user/2007/04/msg03070.html
>>>
>>> Is it a bug?  If so, what package is the culprit?
>> Mounting luks-encrypted partitions works just fine for me.  Make sure
>> to close and teardown all existing mappings (unmount the partition and
>> then run cryptsetup luksClose /dev/mapper/...).  Then run "gnome-mount
>> -t -d /dev/sdb1" (given that sdb1 is the luks encrypted partition).
>> This should prompt you for the password, unlock the key, and then mount
>> /dev/dm-0 at /media/$label_of_your_partition.
>> If you haven't set a label for your partition, it will be mounted at
>> /media/disk.
> 
> After inserting the USB key:
> 
>  % ls -l /dev/sdb
>  brw-rw---- 1 root floppy 8, 16 2007-04-20 07:56 /dev/sdb
>  % ls -l /dev/mapper
>  total 0
>  crw-rw---- 1 root root 10, 63 2007-04-20 07:45 control
>  % gnome-mount -t -d /dev/sdb
>  gnome-mount 0.6
>  libhal-storage.c 1401 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set.
>  Enter password to unlock encrypted data for /dev/sdb:
>  Setup clear-text device for /dev/sdb.
> 
>  ** (gnome-mount:5670): WARNING **: Timeout for waiting for cleartext device... Exiting.
>  % ls -l /dev/mapper
>  total 0
>  crw-rw---- 1 root root  10, 63 2007-04-20 07:45 control
>  brw-rw---- 1 root disk 254,  0 2007-04-20 07:59 luks_crypto_e693fed0-4f6b-4585-9235-3ff92e3ff33d
>  % gnome-mount -t -d /dev/sdb
>  gnome-mount 0.6
>  libhal-storage.c 1401 : INFO: called LIBHAL_FREE_DBUS_ERROR but dbusError was not set.
>  Enter password to unlock encrypted data for /dev/sdb:
> 
>  ** (gnome-mount:5701): WARNING **: Setup failed for /org/freedesktop/Hal/devices/volume_uuid_e693fed0_4f6b_4585_9235_3ff92e3ff33d: org.freedesktop.Hal.Device.Volume.Crypto.SetupError : /dev/sdb is already setup?
> 
> It should turn up as Secret (that's the label), but it clearly doesn't.
> As root I can mount the /deb/mapper/luks_crypto_<guid> device that's
> created.

This is getting offtopc for this list, so I changed to pkg-utopia.

It's most likely a problem within hal or udev.
After unlocking the crypto device, do you have a /dev/dm-0 device?
If not, what does grep dm /etc/udev/rules.d/* say?
Do you have a rule which suppresses the creation of the dm* device? If
so remove that rule.

If that still doesn't help, file a bug report against hal and provide
the information of "hald --daemon=no --verbose=yes".

Cheers,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-utopia-maintainers/attachments/20070420/4dcc6389/signature.pgp