Actually, I am not sure this is a bug in gnome-volume-manager, but a consequence of the distribution policy regarding package “hal”, and more exactly the file /usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi. As per the lines 111 to 124 of that file, fixed partitions included in fstab, not already mounted, and with “noauto” among the mount options, are flagged as volume.ignore = false. gnome-volume-manager then mounts them.
One way to avoid it would be to include in the file /etc/hal/fdi/policy/preferences.fdi (location recommended by the hal documentation, see http://people.freedesktop.org/~david/hal-spec/hal-spec.html#fdi-search-paths) a section as the following one: <device> <match key="linux.fstab.mountpoint" exists="true"> <match key="linux.fstab.options" contains="noauto"> <merge key="volume.ignore" type="bool">true</merge> </match> </match> </device> (There are surely plenty of other “match key” combinations to get the same results). This is, IMHO, what Dirk R. Gently was referring to when he mentioned "blacklist". -- Gnome Volume Manager mistakes Hard Disk Partitions for Removable media https://bugs.launchpad.net/bugs/114822 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-volume-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs