Bug 311171 - extra dialog popup when mounting encrypted device
Summary: extra dialog popup when mounting encrypted device
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-mount
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F8Target
TreeView+ depends on / blocked
 
Reported: 2007-09-28 15:32 UTC by Jeremy Katz
Modified: 2013-03-06 03:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-17 02:07:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
lshal output (122.06 KB, text/plain)
2007-10-11 20:26 UTC, Jeremy Katz 		no flags Details
View All

Description Jeremy Katz 2007-09-28 15:32:08 UTC 
When mounting a luks encrypted partition off of a USB stick, it mounts but you
also get a popup from gnome-mount with

"Cannot mount volume.  Error org.freedesktop.Hal.Device.UnknownError" with
details of "An unknown error occurred"
Comment 1 David Zeuthen 2007-10-11 18:10:09 UTC 
I can't seem to reproduce this... is the file system on the cleartext device
valid? Do you have more than one partition on the USB stick itself? Please
attach lshal output...
Comment 2 Jeremy Katz 2007-10-11 20:26:31 UTC 
Created attachment 224751 [details]
lshal output

There are two partitions on the stick.	One has a live image, the other has an
encrypted directory.  Both are mounted and show up fine other than the fact
that I get the spurious popup

Attaching lshal output (this is post mounting)
Comment 3 Jeremy Katz 2007-10-11 20:28:10 UTC 
And a different encrypted stick which only has one partition is fine, so that
might well be related
Comment 4 David Zeuthen 2007-10-11 21:02:23 UTC 
I tried reproducing this with a similar setup but I don't get the spurious
popup. I'll grab you in the office next week...
Comment 5 Jeremy Katz 2007-10-17 02:07:37 UTC 
Looks fine with rawhide of today.
Note You need to log in before you can comment on or make changes to this bug.