Hide Forgot
I have a number of partitions mounted through pam_mount (i.e. encrypted paritions mounted for each user upon login). These show up in the removable drives list -- they shouldn't (or there should be a configuration to hide them). While they are unmountable, they are not removable; furthermore unmounting is not desirable anyway (they include the users home directory). Querying udevadm shows that the underlying block device is *not* removable: looking at device '/devices/virtual/block/dm-9': KERNEL=="dm-9" SUBSYSTEM=="block" DRIVER=="" ATTR{range}=="1" ATTR{ext_range}=="1" ATTR{removable}=="0" If, in the meantime, there is a hack to set an option or flag such that these mounts are hidden from the removable drive list please let me know. From a UI perspective this is made worse by the removable drive list being the single "simplified" interface in Gnome 3. Unfortunately my users who might otherwise benefit from this simplified interface are completely baffled when they want to remove a USB stick and are confronted by all these mounts that they don't need to know or care about. (In the past they could identify the USB drive on the desktop background and remove from the context menu there).
As I workaround I've created /etc/udev/rules.d/hide_non_removable_disks.rules containing: ATTR{removable}=="0",ENV{UDISKS_PRESENTATION_HIDE}="1" It does the trick -- as in it's cleared the clutter of non-removable drives from the removable drive list -- though I'm not entirely sure this is the Right Thing. It also leaves the nautilus devices section empty until there's a removable drive. Perhaps something more subtle is required. I wasn't sure I could rely on the contents of the KERNEL parameter being constant between boots? (in my case, KERNEL=="dm-9" etc., fished from udevadm info -a -n /dev/mapper/cryptmounted_drive_1 )
(In reply to comment #1) > As I workaround I've created > /etc/udev/rules.d/hide_non_removable_disks.rules containing: > > ATTR{removable}=="0",ENV{UDISKS_PRESENTATION_HIDE}="1" > > It does the trick -- as in it's cleared the clutter of non-removable drives > from the removable drive list -- though I'm not entirely sure this is the > Right Thing. It also leaves the nautilus devices section empty until there's > a removable drive. Perhaps something more subtle is required. I wasn't sure > I could rely on the contents of the KERNEL parameter being constant between > boots? > > (in my case, KERNEL=="dm-9" etc., fished from udevadm info -a -n > /dev/mapper/cryptmounted_drive_1 ) I have encountered the same problem. Althuogh I do not mount (encrypted) partions upon login with pam. I have two harddisks with several partitions. Only a few should show up in nautilus (and desktop background) and they are certainly not mountable or unmountable. Everything worked fine until approx. fedora 12, introdicing policy kit. I than added udev rules ACTION=="add|change" , KERNEL=="sda*" , ENV{UDISKS_PRESENTATION_HIDE}="1" This worked until fedora 17, again showing up all hardisk partitions. Iḿ trying to figure out whether your workaround, the udev rule on attrib removable works. My first attempt was negative. Maybe its caused by some new feature in fc17 something with mounting/unmounting per user. On the internet I can not find a lot of useful information. I think it is not related to encrypted partitions, it is more related to the interpretation of gnome/policy-kit.
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
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.