GNOME Bugzilla – Bug 335162
gnome-volume-manager 2.14 can't mount mount-points included in /etc/fstab
Last modified: 2006-03-23 15:44:51 UTC
Please describe the problem: I just upgraded to gnome 2.14: gnome-volume-manager 1.5.15 gnome-vfs 2.14.0 gnome-mount 0.4 and now automounting cds/dvds (or manual mounting through icons in Computer) doesn't work when my dvd reader and cd-burner are listed in /etc/fstab, with normal permissions that allow mounting by common user (noauto,ro,user): I only get a message telling me that I haven't the needed privileges. If I remove those entries from fstab auto/manual mounting works again, but volumes are mounted to a directory with the cd label name, and I need fixed mount points for other applications (I don't use just gnome) Steps to reproduce: 1. insert a cd with gnome-volume-manager enabled 2. wait for automount to start 3. read the error message Actual results: gnome can't mount the cd Expected results: gnome-volume-manager should mount the cd to /media/cdrom Does this happen every time? yes Other information:
*sigh* someone else complained last week that g-v-m shouldn't mount things in /etc/fstab which is why I fixed it to not do that. anyways... I'd suggest that if you want it to mount your /etc/fstab entries, then you should modify the fdi files in the hal share directory to not set volume.ignore
excuse me, but IMHO this behaviour is wrong. It should be the opposite, at least gnome-mount should use the settings defined in fstab, just like pmount does, and create new mount-points when there aren't previous settings. definining mount-points in fstab is a standard policy in every linux system out there, and gnome-mount forces the users to change defaults that many other programs take for granted
gnome-volume-manager != gnome-mount
s/gnome-mount/gnome-volume-manager/
well, gnome-mount should use the stuff in /etc/fstab if it applies to a volume, sure... but what does that have to do with gnome-volume-manager? g-v-m only decides whether it should mount something automatically or not, not where it should be mounted. since you can write custom fdi files to set volume.ignore to false for the volumes you want to mount, no problem exists in gnome-volume-manager. All gnome-volume-manager does is check the HAL properties on a volume to see if it should be mounted - if the property volume.ignore is set to true, then we don't mount it.
ok, so where should I submit this bug report? there is no gnome-mount product in bugzilla
yea there is...