Bug 488573

Summary: Wrong icon label for mounted filesystem
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: gnome-disk-utilityAssignee: David Zeuthen <davidz>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: davidz, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-03-04 21:39:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Output of "gvfs-mount -li"
none
output of "cat /proc/mounts"
none
Output of "devkit-disks --dump" none

Description Tom London 2009-03-04 20:52:04 UTC
Created attachment 334061 [details]
Output of "gvfs-mount -li"

Description of problem:
I get 2 "copies" of the icon for filesystem mounted when I login to gnome.

Both say "22 GB Filesystem", when in fact, 2 different filesystems have been mounted:

/dev/sda1 on /media/12C4490AC448F211 type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096)
/dev/dm-3 on /media/extra type ext3 (rw,nosuid,nodev,uhelper=devkit)

I just freshly booted and logged in.  My system has the following disk layout:

Partition 1: 22 GB NTFS partition
Partition 2: 41 GB encrypted ext3 partition
Partition 3: /boot
Partition 4/5: Encrypted LVM for /

I attached output of "gvfs-mount -li", output of "cat /proc/mounts".

I need to upgrade devkit-disks to get "--dump" option.  I'll attach that when complete.

Version-Release number of selected component (if applicable):
gnome-disk-utility-0.2-1.fc11.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tom London 2009-03-04 20:52:33 UTC
Created attachment 334062 [details]
output of "cat /proc/mounts"

Comment 2 Tom London 2009-03-04 20:56:37 UTC
Created attachment 334064 [details]
Output of "devkit-disks --dump"

Comment 3 Tom London 2009-03-04 21:04:08 UTC
This doesn't look right to me:

  Volume(0): 22 GB Filesystem
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '12C4490AC448F211'
     unix-device: '/dev/sda1'
    themed icons:  [drive-harddisk-ata]  [drive-harddisk]  [drive]
    can_mount=1
    can_eject=0
    Mount(0): 22 GB Filesystem -> file:///media/extra
      Type: GProxyMount (GProxyVolumeMonitorGdu)
      themed icons:  [drive-harddisk-ata]  [drive-harddisk]  [drive]
      can_unmount=1
      can_eject=0
      is_shadowed=0
  Volume(1): 41 GB Encrypted
    Type: GProxyVolume (GProxyVolumeMonitorGdu)
    ids:
     uuid: '49955702-1c8b-4f5b-9ab3-0ce4ee2873e9'
     unix-device: '/dev/sda2'
    can_mount=1
    can_eject=0

In fact, the first "Volume" (22 GB NTFS) is mounted as '/media/12C4490AC448F211', not '/media/extra'.

The second "Volume" (41 GB Encrypted) is mounted as '/media/extra'.....

Comment 4 Tom London 2009-03-04 21:29:31 UTC
A bit more info:

I ran into this after I changed the "authorizations" to allow mounting 'system-internal device'.

This allows /dev/sda1 (the NTFS FS) and /dev/sda3 (the encrypted FS) to be "automagically" mounted on login.

The LUKS passphrase for /dev/sda3 -> /dev/dm-3 is in my gnome-keyring.

Comment 5 David Zeuthen 2009-03-04 21:39:13 UTC
Looks like this is a dup of bug 488399, please try the updated gvfs packages there. Thanks!

*** This bug has been marked as a duplicate of bug 488399 ***