Bug 532594

Summary:	No password prompt when USB stick encrypted with cryptsetup-luks is inserted
Product:	[Fedora] Fedora	Reporter:	Andriy Tsykholyas <andriy.tsykholyas>
Component:	DeviceKit-disks	Assignee:	David Zeuthen <davidz>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	agk, davidz, dwysocha, lvm-team, mbroz, mclasen, opensource, pjones, prockai, whulbert
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-11-03 14:50:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.