Bug 415161 - gnome-mount failed to mount luks encrypted disk
gnome-mount failed to mount luks encrypted disk
Product: Fedora
Classification: Fedora
Component: gnome-mount (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-12-06 21:33 EST by Stefan Jensen
Modified: 2013-03-05 22:53 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-09 00:26:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Stefan Jensen 2007-12-06 21:33:54 EST
Description of problem:

gnome-mount can not mount a luks encrypted disk as user.

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


How reproducible:


Steps to Reproduce:

1. create a encrypted disk e.g: /dev/sdb2 with luks header.
2. try to mount it as user via "drivemount_applet2" or via command line
3. after succesfull auth, disk is not mounted,
/dev/mapper/luks_crypto_xxxxxxxxxx is not created.
Actual results:

Disk not mounted, and not accessible.

Expected results:

Disk mounted and accessible.

Additional info:

$ /usr/bin/gnome-mount --hal-udi /org/freedesktop/Hal/devices/volume_uuid_xxxxxxxxxx
will fail, same results as above, but:

$ sudo /usr/bin/gnome-mount --hal-udi
works like expected. Disk will mount and is accessible.
Comment 1 Stefan Jensen 2008-01-23 03:00:24 EST

just found out, that PolicyKit prevents mounting the luks_crypto. Seems that no
policy or maybe wrong policy exist for a internal luks disk.

Anyway, I would expect in this situation, that i will be asked for a root
password, rather than silently refuse the setup of the device (?)

$ /usr/bin/gnome-mount -v -t --hal-udi

** (gnome-mount:3570): WARNING **: Setup failed for
org.freedesktop.Hal.Device.PermissionDeniedByPolicy :
org.freedesktop.hal.storage.crypto-setup-fixed auth_admin_keep_always <--
(action, result)

best regards

Comment 2 Michel Alexandre Salim 2008-08-26 16:51:55 EDT

I opened a similar bug report for Rawhide:

(probably a different bug, considering gnome-mount works in F10 alpha IIRC)
Comment 3 Bug Zapper 2008-11-26 03:52:41 EST
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-01-09 00:26:49 EST
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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