Do not show LUKS devices of internal mounted disks

Bug #441211 reported by llimaa on 2009-10-03
This bug affects 33 people
Affects Status Importance Assigned to Milestone
devicekit-disks (Fedora)
Won't Fix
udisks (Ubuntu)

Bug Description

Binary package hint: nautilus

In Karmic Beta 1:

Nautilus shows useless unfunctional disk entry for LVM2 logical volume of root that is inside a crypted device (dm-crypt).
It has a lock symbol on the icon and is totaly useless because the root volume is already unlocked and does not need to show up.

When i click on it, a password prompt appears and when i type the password nothing happens. Of course nothing has to happen, because its already unlocked and does not have to show up in nautilus because the "Filesystem Icon already is a link to root volume of lvm2.

I think it's because of the new DeviceKit.

My fstab to show disk setup:
proc /proc proc defaults 0 0
# / was on /dev/mapper/vg--xstation-lv--root during installation
UUID=05416132-988c-4a26-a1c9-8e10dc73a63b / ext4 relatime,errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=d64d7a3f-d856-4f48-9f50-e50036c60c87 /boot ext4 relatime 0 2
/dev/mapper/sda3_crypt /media/storage ext4 relatime 0 2
# swap was on /dev/mapper/vg--xstation-lv--swap during installation
UUID=9d911269-d60d-4396-97bf-bef717e71b3c none swap sw 0 0
/dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0

Created attachment 354517
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.

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.

Created attachment 354742
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.

llimaa (llimaa) wrote :
description: updated
llimaa (llimaa) on 2009-10-03
description: updated
llimaa (llimaa) on 2009-10-03
description: updated
llimaa (llimaa) on 2009-10-03
description: updated
affects: nautilus (Ubuntu) → devicekit-disks (Ubuntu)
Martin Pitt (pitti) on 2009-10-11
summary: - Karmic beta 1 has useless unfunctional disk entries in nautilus
+ Do not show LUKS devices of internal mounted disks
Changed in devicekit-disks (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Changed in devicekit-disks (Fedora):
status: Unknown → Confirmed

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.

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.

Lando Nachtmann (lanna) wrote :

Any news here lately? I guess I have this problem, too:
LUKS-encrypted partitions (without LVM here). They get mounted on login via pam_mount, but these -- already mounted -- devices show up as 'X GB Filesystem's in the file browser. Extremely irritating...

Martin Pitt (pitti) on 2010-02-15
affects: devicekit-disks (Ubuntu) → udisks (Ubuntu)

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:

Viktor Pal (deere) wrote :
Viktor Pal (deere) wrote :

I can confirm the problem on Ubuntu 10.04.
nautilus and Places Menu shows LVM2 Physical Volume in Gnome.
I also use dm-crypt for the device.
There is no lock on the device I can click on it, but after clicking I get
"Unable to mount 97 GB LVM2 Physical Volume"
"Not a mountable file system"

Please see attached image previous post.

I agree that is irritating.
Do not show LUKS devices of internal mounted disks .

Viktor Pal (deere) wrote :

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.

Just confirming this is still a problem with Ubuntu 10.10 RC, LVM inside an encrypted partition.

Alan Porter (alan.porter) wrote :

Still in 10.10 proper. I see one entry for the encrypted LVM physical volume, and another entry for an LV that is a LUKS volume. Looking for a real solution, or even for a clumsy work-around (such as putting some entry in /etc/fstab to mask the volumes from nautilus's view).

Erik Wognsen (r4mses) wrote :

Still in Ubuntu 11.04 for me. Nautilus shows me a "8,3 GB LVM2 Physical Volume" and when clicking on it, a dialog appears: "Unable to mount [...] Not a mountable file system".

Matt Wheeler (funkyhat) wrote :

This is still an issue in Ubuntu 12.04

Tyler Wagner (tyler) wrote :

Confirmed, still persists under Ubuntu 12.04. See attached.

Changed in devicekit-disks (Fedora):
importance: Unknown → Medium
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.