Bug 532594 - No password prompt when USB stick encrypted with cryptsetup-luks is inserted
Summary: No password prompt when USB stick encrypted with cryptsetup-luks is inserted
Keywords:
Status: CLOSED DUPLICATE of bug 531992
Alias: None
Product: Fedora
Classification: Fedora
Component: DeviceKit-disks
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-02 22:29 UTC by Andriy Tsykholyas
Modified: 2013-03-06 03:59 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-03 14:50:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Andriy Tsykholyas 2009-11-02 22:29:11 UTC 
Description of problem:
This problem exists on both i386 and x86_64 Fedora 12 beta. 
After insertion of USB stick encrypted with cryptsetup-luks there is no password prompt to unlock it.

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


How reproducible:
Insert USB stick encrypted with cryptsetup-luks.

 
Actual results:
No password prompt is displayed.

Expected results:
Password prompt should be displayed to the user. As it currently does on my Fedora 10 box.


Additional info:
The USB stick becomes present in /dev after insertion and can be mounted manually.
I'm not sure I've selected correct component.
Comment 1 Milan Broz 2009-11-03 09:40:37 UTC 
I am also not sure if DevKit-disks, gnome-mount or whatever is responsible here - reassigning ro devkit, please correct me if I am mistaken:-)
Comment 2 David Zeuthen 2009-11-03 14:50:34 UTC 
Looks like a duplicate of bug 531992 - if 'BLKID_DEBUG=0xffff blkid -p <device>' prints out something like "ambivalent result" it is. Otherwise please reopen (and paste the blkid output here). Thanks.

*** This bug has been marked as a duplicate of bug 531992 ***
Comment 3 Andriy Tsykholyas 2009-11-03 15:25:11 UTC 
Yeap, this is a duplicate of bug 531992.
Note You need to log in before you can comment on or make changes to this bug.