Bug#408714: libgnomevfs2-0: Irrelevant volume listed on computer:///
joss at debian.org
Wed Jan 31 00:33:25 CET 2007
Le samedi 27 janvier 2007 à 22:11 +0100, Roland Mas a écrit :
> My Nautilus computer:/// windows shows an extraneous "972.7 MB Volume"
> icon in addition to the normal floppy, CD, filesystem and network
> icons. Trying to open/browse that volume fails, with an error message
> mentioning that /dev/hdc1 is not removable. That's correct, it's not
> removable; it's even part of my /dev/md0 RAID1 array, which is used as
> my root filesystem. I can't understand why hdc1 would be displayed
> and not hda1 (the other half of the mirror) or other hdc* partitions
> (which are in turn used in other RAID arrays).
> From a few bug reports I've read, here's some info that could be
> * /dev/hdc1 isn't mentioned in /dev/fstab at all, nor is it mounted
> * "gnomefvs-ls computer:///" does list that volume.
> * lshal shows no differences between /dev/hda* and /dec/hdc*, apart
> from the fact that the "udi = " values for hda* have an extra "_0"
> when compared with their hdc* equivalents; here are a few selected
> udi = '/org/freedesktop/Hal/devices/storage_serial_L6116LHH'
> block.device = '/dev/hda' (string)
> udi = '/org/freedesktop/Hal/devices/volume_uuid_bf80262d_2f31_44f7_87a3_a788b281fdbf_0'
> block.device = '/dev/hda1' (string)
> udi = '/org/freedesktop/Hal/devices/storage_serial_L6118B6H'
> block.device = '/dev/hdc' (string)
> udi = '/org/freedesktop/Hal/devices/volume_uuid_bf80262d_2f31_44f7_87a3_a788b281fdbf'
> block.device = '/dev/hdc1' (string)
> I'd appreciate pointers on how to help debug that.
Unfortunately I don't have a RAID setup so it will be hard to reproduce
I'd start by checking everything is fine on the kernel/udev side, e.g.
same permissions and owners on the devices. You can also check that
pmount-hal correctly refuses to mount all these partitions.
The next step is to check with gnome-vfs 2.16 in experimental. I don't
think there are much relevant changes between 2.14 and 2.16, but there's
more chance to get interest from upstream developers in this case.
Then, you can rebuild gnome-vfs2 with -DHAL_SHOW_DEBUG; gnomevfs-ls and
nautilus should then show relevant information in stdout. There's much
chance that HAL returns drives it shouldn't return, but you will
probably be able to see if gnome-vfs is able to filter out other
If this is not enough, I guess you'll have to end up installing
libgnomevfs2-0-dbg and check what is happening in the _hal_update_all
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Ceci est une partie de message
Url : http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20070131/d1764d0c/attachment.pgp
More information about the Pkg-gnome-maintainers