Bug 241869 - Error message on mounting crypto volumes (but no error)
Error message on mounting crypto volumes (but no error)
Product: Fedora
Classification: Fedora
Component: gnome-mount (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Depends On:
  Show dependency treegraph
Reported: 2007-05-31 05:27 EDT by Tim Niemueller
Modified: 2013-03-05 22:50 EST (History)
1 user (show)

See Also:
Fixed In Version: 0.6-2.fc7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-09-11 17:42:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot showing the error messages (52.85 KB, image/png)
2007-05-31 05:27 EDT, Tim Niemueller
no flags Details

  None (edit)
Description Tim Niemueller 2007-05-31 05:27:38 EDT
Description of problem:
If an external drive is inserted which contains only a LUKS partition the key is
queried properly and the drive is mounted correctly. g-v-m (I suspect that it is
g-v-m, also it could be related to hal) shows an error message for an "unknown
error", but the drive is mounted and accessible.

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

How reproducible:

Steps to Reproduce:
1. Insert external drive with just a LUKS partition
2. Enter key
3. See g-v-m mount the drive and then spit an error message
Actual results:
Error messages.

Expected results:
No error messages.

Additional info:
See screenshot for error messages. I wiped out the UDI.

The UDI in the error message is the UDI of the mounted unencrypted file system
that resides in the LUKS partition.
Comment 1 Tim Niemueller 2007-05-31 05:27:41 EDT
Created attachment 155786 [details]
Screenshot showing the error messages
Comment 2 David Zeuthen 2007-05-31 10:41:21 EDT
Huh, funny. That's actually a gnome-mount bug so reassigning!
Comment 3 Tim Niemueller 2007-09-11 17:42:37 EDT
Seems to be fixed in F7, I cannot reproduce this anymore. Closing.

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