Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. setup a luks USB key eg http://www.saout.de/tikiwiki/tiki-index.php?page=EncryptedDeviceUsingLUKS 2. plug disk into usb port. Gnome prompts for LUKS password. Authentication is ok 3. Disk is not mounted. But... [root@datou ~]# cryptsetup luksOpen /dev/sdc1 sdc1 Command failed: Device already exists [root@datou ~]# cryptsetup luksClose sdc1 [root@datou ~]# cryptsetup luksOpen /dev/sdc1 sdc1 Enter LUKS passphrase: key slot 0 unlocked. Command successful. [root@datou ~]# mount /dev/sdc1 /media/emount mount: /dev/sdc1 already mounted or /media/emount busy Actual results: Mounting from the command line works if Gnome does not get the chance to lock the disk first. If Gnome gets a chance to attempt mount than it locks up the disk. Expected results: Disk should mount in Gnome once authentication has succeeded but does not. Additional info:
I've noticed the same problem under RHEL5.
Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and will not be fixed by Fedora. Therefore we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen thus bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.