Bug 748177

Summary: Can't mount filesystems on a LUKS-encrypted LVM volume from nautilus
Product: [Fedora] Fedora Reporter: Yann Droneaud <yann>
Component: nautilusAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: ccecchi, tbzatek, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 22:36:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Error shown by Nautilus when trying to access to the unlocked LUKS volume
none
After manually update volume group information none

Description Yann Droneaud 2011-10-22 19:28:18 UTC
After booting Fedora-16-TC-x86_64-Live-Desktop, I have tried to access
to the computer main filesystems ("non live").
Those filesystem reside on a LVM2 volume group (VG) using encrypted (LUKS) physical volume (PV) which was setup by Fedora installer (F14).

Nautilus shows the disk, allows me to unlock it (entering passphrase), but can't go further. No new filesystem is shown by Nautilus.

Comment 1 Yann Droneaud 2011-10-22 19:29:57 UTC
Created attachment 529635 [details]
Error shown by Nautilus when trying to access to the unlocked LUKS volume

Comment 2 Yann Droneaud 2011-10-22 19:35:14 UTC
Created attachment 529636 [details]
After manually update volume group information

After running vgscan & vgchange

# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "vg_deela" using metadata type lvm2

# vgchange -a y vg_deela
  3 logical volume(s) in volume group "vg_deela" now active


The filesystems are now available in Nautilus.

Comment 3 Fedora End Of Life 2013-01-16 17:45:20 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Fedora End Of Life 2013-02-13 22:36:22 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.