Hide Forgot
Created attachment 535048 [details] udisks --dump Description of problem: At least since the beta of F16 I have noticed that my system shows a "removable devices" even when I have no such devices plugged in. After I noticed that palimpsest reported my luks partition wrong, I tried launching "udevadm trigger" from a terminal, and all of a sudden palimpsest reports stuff right, and the "Removable devices" icon disappear. Version-Release number of selected component (if applicable): udev-173-3.fc16.x86_64 udisks-1.0.4-3.fc16.x86_64 kernel-3.1.1-2.fc16.x86_64 How reproducible: Always Steps to Reproduce: 1. Partiton your system with crypted partitons without LVM 2. Start your system 3. Actual results: udisks picks up the wrong information Expected results: Everything is reported right Additional info: My computer has a HDD at 500GB, partitoned with three primary partiotns (the two first being windows 7, and the third being a Fedora boot partition), and two luks-crypted logical (a swap and a btrfs Fedora root partition). this is the difference in udisks --dump before and after the trigger. [xake@ferra ~]$ diff -u udisks-before udisks-after --- udisks-before 2011-11-22 15:20:46.919326676 +0100 +++ udisks-after 2011-11-22 15:21:00.443880569 +0100 @@ -70,25 +70,9 @@ version: uuid: 4c86ad4c-0d71-48a3-8cd2-058cccda2a07 label: - drive: - vendor: - model: - revision: - serial: - WWN: - detachable: 0 - can spindown: 0 - rotational media: Yes, unknown rate - write-cache: unknown - ejectable: 0 - adapter: Unknown - ports: - similar devices: - media: - compat: - interface: (unknown) - if speed: (unknown) - ATA SMART: not available + cleartext luks device: + backed by: /org/freedesktop/UDisks/devices/sda6 + unlocked by: uid 0 ======================================================================== I attach the "before" file for completeness.
I have the same problem. My LUKS encrypted partition is being shown in 'Removable Devices' in Gnome 3.0. However my disk layout is different: Device Boot Start End Blocks Id System /dev/sda1 * 2048 616447 307200 83 Linux /dev/sda2 616448 234440703 116912128 8e Linux LVM where: /dev/sda1 is /boot /dev/sda1 is a PV, on which a single vg is created with 3 lvs: for '/', swap and 'home'. on lvhome I've got a LUKS encrypted partition which is finally mounted as: /dev/mapper/luks-<id> /home
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
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.