Oddly, sometimes I get a failure and sometimes a success, with the exact same hardware and software. I'm posting a trace of each in the hope that it will shed some light on this for someone.
Success: eande...@eric-laptop:~/tmp$ gnome-mount -dvtb /dev/sdb3 gnome-mount 0.8 ** (gnome-mount:15840): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d' Enter password to unlock encrypted data for /dev/sdb3: ** (gnome-mount:15840): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d for crypto Setup clear-text device for /dev/sdb3. ** (gnome-mount:15840): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d.. ** (gnome-mount:15840): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_part_1_size_0 ** (gnome-mount:15840): DEBUG: In crypto_setup_device_removed for /org/freedesktop/Hal/devices/volume_part_1_size_0 ** (gnome-mount:15840): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 ** (gnome-mount:15840): DEBUG: /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 is backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d - will mount Clear text device is /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d. Mounting. ** (gnome-mount:15840): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 ** (gnome-mount:15840): DEBUG: read mount point 'usb_crypto' from gconf string key '/system/storage/volumes/_org_freedesktop_Hal_devices_volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5/mount_point' ** (gnome-mount:15840): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_a7d1a59a_2a6a_4487_a246_9740ebd253a5 with mount_point='usb_crypto', fstype='', num_options=0 Mounted /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d at "/media/usb_crypto" eande...@eric-laptop:~/tmp$ Failure: eande...@eric-laptop:~/tmp$ gnome-mount -dvtb /dev/sdb3 gnome-mount 0.8 ** (gnome-mount:15769): DEBUG: Crypto volume - UDI '/org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d' Enter password to unlock encrypted data for /dev/sdb3: ** (gnome-mount:15769): DEBUG: Setting up /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d for crypto Setup clear-text device for /dev/sdb3. ** (gnome-mount:15769): DEBUG: Waiting for cleartext volume backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d.. ** (gnome-mount:15769): DEBUG: In crypto_setup_device_added for /org/freedesktop/Hal/devices/volume_part_1_size_0 ** (gnome-mount:15769): DEBUG: /org/freedesktop/Hal/devices/volume_part_1_size_0 is backed by /org/freedesktop/Hal/devices/volume_uuid_9af283ce_4e82_4341_b8b1_6b19e232388d - will mount Clear text device is /dev/mapper/luks_crypto_9af283ce-4e82-4341-b8b1-6b19e232388d. Mounting. ** Message: /org/freedesktop/Hal/devices/volume_part_1_size_0 does not have a mountable filesystem -- Gnome-mount will only mount encrypted partitions and not drives created with cryptsetup/luks https://bugs.launchpad.net/bugs/117011 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
