After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 624067 - Do not show an icon for mounting unlocked and already mounted luks volumes.
Do not show an icon for mounting unlocked and already mounted luks volumes.
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: [obsolete] gdu volume monitor
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2010-07-10 21:12 UTC by Hussam Al-Tayeb
Modified: 2018-04-14 17:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30

Attachments
nautilus showing bug (69.48 KB, image/png)
2010-07-10 21:12 UTC, Hussam Al-Tayeb 		Details
gvfs output (1.80 KB, text/plain)
2010-08-10 15:31 UTC, Hussam Al-Tayeb 		Details
/etc/mtab (559 bytes, text/plain)
2010-08-10 15:32 UTC, Hussam Al-Tayeb 		Details
/etc/fstab (527 bytes, text/plain)
2010-08-10 15:32 UTC, Hussam Al-Tayeb 		Details
udisks --dump and other data (117.26 KB, text/plain)
2010-08-10 16:23 UTC, Hussam Al-Tayeb 		Details

Description Hussam Al-Tayeb 2010-07-10 21:12:29 UTC 
Created attachment 165646 [details]
nautilus showing bug

nautilus shows extra useless icons for unlocked luks encrypted volumes.

gvfs 1.6.2
nautilus 2.30.1
udisks 1.0.1
gnome-disk-utility 2.30.1

In the attached screenshot, "40 GB Hard Disk: 36 GB Filesystem"   is the root disk and nautilus allows me to access it from 'File System' icon.
But an extra "40 GB Hard Disk: 36 GB Filesystem" shows. if I double click on it, it tells me /dev/dm-0 is already mounted which is true.

This wasn't an issue when gnome used hal.
Comment 1 Hussam Al-Tayeb 2010-07-10 21:18:47 UTC 
Forgot to add udev verion is 159 but it happened with older udev versions as well.
Comment 2 Hussam Al-Tayeb 2010-08-10 03:26:24 UTC 
Could this be a gdu or udisks or udev problem? Any advice?
Comment 3 Hussam Al-Tayeb 2010-08-10 15:31:31 UTC 
Created attachment 167523 [details]
gvfs output
Comment 4 Hussam Al-Tayeb 2010-08-10 15:32:05 UTC 
Created attachment 167524 [details]
/etc/mtab
Comment 5 Hussam Al-Tayeb 2010-08-10 15:32:37 UTC 
Created attachment 167525 [details]
/etc/fstab
Comment 6 Hussam Al-Tayeb 2010-08-10 16:23:20 UTC 
Created attachment 167531 [details]
udisks --dump and other data
Comment 7 Hussam Al-Tayeb 2010-09-22 15:11:27 UTC 
I think I have identified what the problem is. 
gdu doesn't understand when luks encrypted volumes are unlocked/mounted at boot before gnome starts.
If I unmount/lock my home partition and log in as root into gnome then use gnome to unlock my home partition and mount it, the problem disappears.
But this isn't very useful because I need my disk unlocked/mounted at boot normally so I can log into a normal user.
Again, I don't know much about this and my English can be confusing. Can gdu be able to tell that a luks device was already unlocked/mounted earlier before gnome-session started?
Comment 8 Ondrej Holy 2018-04-13 18:15:10 UTC 
Gdu volume monitor has been superseded by udisks2 volume monitor long time ago. I am closing this bug because many have been changed since this was reported. If this is still an issue with the recent gvfs releases, please reopen and change component to udisks2 volume monitor.
Comment 9 Hussam Al-Tayeb 2018-04-14 17:41:42 UTC 
This was indeed a very old bug report. It works as expected in current gvfs releases. Thank you.