Bug 513009 - Nautilus shows LUKS devices which should be hidden
Summary: Nautilus shows LUKS devices which should be hidden
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 11
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-21 16:31 UTC by Stephen
Modified: 2013-03-06 03:58 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 13:45:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
screenshot of luks devices in nautilus (291.74 KB, image/png)
2009-07-21 16:31 UTC, Stephen
no flags Details
output of devkit-disks --dump, and rpm versions (17.18 KB, text/plain)
2009-07-22 17:12 UTC, Stephen
no flags Details

Description Stephen 2009-07-21 16:31:24 UTC
Created attachment 354517 [details]
screenshot of luks devices in nautilus

Description of problem:

Nautilus shows icons for LUKS devices in the 'computer' view.  These devices are LVM volumes within a partition on the internal disk of a laptop.  They are unlocked and the file systems within are mounted as /home and swap.

The LUKS block devices should not be shown in this view as there is nothing you can reasonably do with them.

They are also extremely confusing when you are just trying to navigate your root file system and your USB drives.

In the attached screenshot from my laptop the confusion is aggravated by the crazy-long name given to the first partition on the disk with contains the original old windows install.  But it could be worse.  The other day I installed Fedora 11 onto a new Eeepc for someone. The existing disk layout happened to have a second NTFS partition for Windows snapshots, plus a recovery partition.  I installed into the snapshot partition.  The end result was 2 'padlock' disks, 2 '160GB ATA 12345...' disks, and 'Filesystem'.  I found it difficult to explain which bits were to never be touched.

Anyway, at a minimum, the LUKS devices should not be shown for / or /home which you are extremely unlikely to want to unmount.

This problem surfaced in F10. F9 was OK. It is now present in F11.

Comment 1 Tomáš Bžatek 2009-07-22 15:28:22 UTC
Can you please attach output of `devkit-disks --dump`?
Also please report versions of gvfs, gnome-disk-utility and DeviceKit-disks packages.

In F11 we use completely different stack than F10, perhaps you're facing the same issue from two different subsystems.

Comment 2 Stephen 2009-07-22 17:12:10 UTC
Created attachment 354742 [details]
output of devkit-disks --dump, and rpm versions

Attached requested info.

Problem is definitely present in both F10 and F11.  I'm pretty sure it was not present in F9, as that is the first time LUKS was available in the installer IIRC, and when I started using it.  I distinctly remember noticing the new LUKS device icons after reinstalling with F10 when it came out.

Comment 3 Michael Monreal 2009-10-19 21:06:09 UTC
I have a similar problem here, already on F11.92: I have a few LUKS partitions that I _don't_ automount but don't want to have in that list anyway, I have scripts to mount them and set up stuff. Having "X GB Encrypted" listed there is just not helpful in my case.

What I tried is doing the same that works for non-LUKS partitons: listing them in /etc/fstab. I inserted UUID=... lines for both but nautilus still displays them. 

I know that listing the LUKS partitons in fstab directly does not actually work like that but nautilus should just take this as "this is managed by the user, don't show it" and be consistent with other partition types.

Comment 4 Michael Monreal 2009-10-20 15:44:08 UTC
Today I found out that /etc/cryptab can hold "noauto" lines. So I think the clean solution would be to disregard crypto devices that are already defined in /etc/cryptab, just like what is the case for non-encrypted devices from /etc/fstab.

Comment 5 Bug Zapper 2010-04-27 15:49:50 UTC
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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

Comment 6 Bug Zapper 2010-06-28 13:45:18 UTC
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.