GNOME Bugzilla – Bug 505214
gvfs based Nautilus ignores hal volume.ignore when displaying icons on the desktop
Last modified: 2009-01-10 04:16:26 UTC
Please describe the problem: I have several partitions that I don't wish to displayed as icons on the desktop. In recent nautilus/gnome-vfs-daemon setups, I has able to set the hal property volume.ignore to true, and that partition would no longer be displayed on the desktop. When I upgraded to nautilus/gvfs, these icons returned Steps to reproduce: 1. Have a partition with the hal property volume.ignore=tue 2. Start Nautilus Actual results: Icon for the 'ignored' partition is shown Expected results: There would be no icon displayed for the partition Does this happen every time? Yes Other information: I didn't know if this bug should be raised against Nautilus, or if it was a gvfs bug. Here are the HAL properties from one of the partitions that should not be displayed udi = '/org/freedesktop/Hal/devices/volume_uuid_df9a178b_4f57_4a3f_b14e_bf321b4009e9' block.device = '/dev/sda7' (string) block.is_volume = true (bool) block.major = 8 (0x8) (int) block.minor = 7 (0x7) (int) block.storage_device = '/org/freedesktop/Hal/devices/storage_serial_SFUJITSU_MAF3364LC_00008271' (string) info.capabilities = {'volume', 'block'} (string list) info.category = 'volume' (string) info.interfaces = {'org.freedesktop.Hal.Device.Volume'} (string list) info.parent = '/org/freedesktop/Hal/devices/storage_serial_SFUJITSU_MAF3364LC_00008271' (string) info.product = 'iso' (string) info.udi = '/org/freedesktop/Hal/devices/volume_uuid_df9a178b_4f57_4a3f_b14e_bf321b4009e9' (string) linux.hotplug_type = 3 (0x3) (int) linux.sysfs_path = '/sys/block/sda/sda7' (string) org.freedesktop.Hal.Device.Volume.method_argnames = {'mount_point fstype extra_options', 'extra_options', 'extra_options'} (string list) org.freedesktop.Hal.Device.Volume.method_execpaths = {'hal-storage-mount', 'hal-storage-unmount', 'hal-storage-eject'} (string list) org.freedesktop.Hal.Device.Volume.method_names = {'Mount', 'Unmount', 'Eject'} (string list) org.freedesktop.Hal.Device.Volume.method_signatures = {'ssas', 'as', 'as'} (string list) storage.model = '' (string) volume.block_size = 512 (0x200) (int) volume.fstype = 'ext3' (string) volume.fsusage = 'filesystem' (string) volume.fsversion = '1.0' (string) volume.ignore = true (bool) volume.is_disc = false (bool) volume.is_mounted = true (bool) volume.is_mounted_read_only = false (bool) volume.is_partition = true (bool) volume.label = 'iso' (string) volume.linux.is_device_mapper = false (bool) volume.mount.valid_options = {'ro', 'sync', 'dirsync', 'noatime', 'nodiratime', 'noexec', 'quiet', 'remount', 'exec', 'acl', 'user_xattr', 'data='} (string list) volume.mount_point = '/mnt/iso' (string) volume.num_blocks = 4208967 (0x403947) (int) volume.partition.media_size = 36434698240 (0x87bad6000) (uint64) volume.partition.number = 7 (0x7) (int) volume.partition.start = 23096618496 (0x560aa6e00) (uint64) volume.size = 2154991104 (0x80728e00) (uint64) volume.unmount.valid_options = {'lazy'} (string list) volume.uuid = 'df9a178b-4f57-4a3f-b14e-bf321b4009e9' (string)
This should be handled by the hal volume monitor, reassigning to gvfs.
So, i think we ignore GVolumes with ignore = true, but maybe not GMounts?
I think this is a duplicate of bug 520851 - Stephen, is this device in your /etc/fstab file?
No response in a long time, I guess we should assume it is a dupe. *** This bug has been marked as a duplicate of 520851 ***