GNOME Bugzilla – Bug 332906
drivemount applets adds another (superfluous) icon for usb devices
Last modified: 2008-09-06 19:08:00 UTC
Please describe the problem: I have a USB harddrive with this entry in /etc/fstab: /dev/disk/by-id/usb-SAMSUNG_SV1604N_DEF10AFD02B9-part1 /mnt/fw2 reiserfs defaults,user,noauto 0 0 The drivemount applet shows this mount point as an icon when the drive is absent. When I plugin the drive, the drivemount applet adds another icon named as "149,0 GB-Datenträger". If I click on that new icon and say "mount" then it mounts that drive to /mnt/fw2. So somehow, drivemount applet is able to parse /etc/fstab to figure out the correct mount point? If so, why does it add another icon instead of using the already existing one for the mount point? Steps to reproduce: 1. Create entry in /etc/fstab with /dev/disk/by-id/usb-.... device 2. Plug in that device Actual results: Expected results: Does this happen every time? Other information:
It sounds like it is getting the extra one from HAL, probably because HAL is seeing a different device. In this day and age, you could let HAL, udev and gnome-volume-manager deal with mounting the device for you. Otherwise, we just believe what we are told by GNOME-VFS, reassigning there.
Confirming the bug on ubuntu feisty. Please read https://bugs.launchpad.net/ubuntu/+source/gnome-vfs2/+bug/42017 and my comment there, it describes, what actually goes wrong. A short summary: At the instant gnome-vfs starts and the device listed in /etc/fstab is not available (e.g. because the device-file is not there yet), gnome-vfs creates an user_visible drive entry. Now when the usb drive is plugged in, gnome-vfs gets notified by HAL. Unfortunately, gnome-vfs does not check if it already lists this drive. The devices which were not available the last time gnome-vfs checked should be rechecked and the entry should be reused/altered or removed then. killall gnome-vfs-daemon after plugging in helps here. gnome-vfs then successfuly realizes that its the same drive.
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome. If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs. @Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together. General further information: http://en.wikipedia.org/wiki/GVFS Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html