Bug 213801 - Encrypted removable media not automounted after opening
Summary: Encrypted removable media not automounted after opening
Keywords:
Status: CLOSED DUPLICATE of bug 216538
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-volume-manager
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-11-03 00:39 UTC by Michael Hampton
Modified: 2013-03-06 03:47 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-11-21 01:07:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michael Hampton 2006-11-03 00:39:23 UTC
Description of problem:

After inserting a removable USB drive, its partition is automounted with the
logged-in user's permissions, and an icon for the partition appears on the
desktop. However, after inserting a removable USB drive with a LUKS encrypted
partition, gnome-volume-manager prompts for the passphrase, creates a dm-crypt
mapping, but fails to automount the mapped partition.

Version-Release number of selected component (if applicable):

gnome-volume-manager-2.15.0-2.fc6

How reproducible:

Always

Steps to Reproduce:
1. Create an encrypted partition on a USB flash drive:
   cryptsetup luksFormat /dev/sda1 # Set a passphrase.
   cryptsetup luksOpen /dev/sda1 usbdisk # Enter passphrase.
   mkdosfs -n MyUSBDdrive -F32 /dev/mapper/usbdisk # Could also be ext2 or whatever
   cryptsetup luksClose usbdisk
   eject /dev/sda # And remove the USB flash drive
2. Insert USB flash drive. Passphrase prompt appears. Type in passphrase.
3. Mapping /dev/mapper/luks_crypto_{uuid} is created.
  
Actual results:

The mapping /dev/mapper/luks_crypto_{uuid} is not automatically mounted.

Expected results:

The mapping /dev/mapper/luks_crypto_{uuid} should be mounted at
/media/MyUSBDrive and a desktop icon presented to the user.

Additional info:

Comment 1 W. Michael Petullo 2006-11-21 00:59:10 UTC
Michael, could you mark this as a duplicate of 216538?  I know this report was
entered first, but I think 216538 diagnoses the cause.

Comment 2 Michael Hampton 2006-11-21 01:07:26 UTC
Sure, if I can manage to type the number correctly.

*** This bug has been marked as a duplicate of 216538 ***


Note You need to log in before you can comment on or make changes to this bug.