GNOME Bugzilla – Bug 615267
with gdu newer than 2.28.X nautilus doesn't show mounts on "Resources"
Last modified: 2010-04-09 16:27:33 UTC
with gdu newer than 2.28.X nautilus doesn't show mounts on "Resources" My pc is in a LAN that has also a VPN connection with another LAN. I have setted at boot time several mountpoint of network shares, both NFS and SMB. Starting from versione 2.29.X i don't see those mounts represented as Devices in the "Resources" panel of Nautilus. Anyway the mounts are present ad working if i go to /media folder. I i downgrade GDU to 2.28 those devices reappear.
Sounds like a GVfs gdu volume monitor problem to me. Please attach /etc/fstab and output of 'gvfs-mount -li'.
Created attachment 158302 [details] This is my fstab Please note that my LAN subnet is 172.17346.X , so the addresses with the 10.77.X mask are remote addresses that I access via VPN
If I execute 'gvfs-mount -li' with GDU 2.30 i receive this error message gvfs-mount:10075): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Otherwise if I execute the same command with GDU 2.28 and no difference in other packages I have this answer : (gvfs-mount:10152): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 11 Volume(0): home_bestione Type: GUnixVolume ids: nfs-mount: 'bestione:/home/hutch' themed icons: [drive-removable-media] [drive-removable] [drive] can_mount=1 can_eject=0 should_automount=1 Mount(0): home_bestione -> file:///home/hutch/home_bestione Type: GUnixMount default_location=file:///home/hutch/home_bestione themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(1): backup -> file:///media/backup Type: GUnixMount default_location=file:///media/backup themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(2): packages -> file:///media/packages Type: GUnixMount default_location=file:///media/packages themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(3): packages_orzinuovi -> file:///media/packages_orzinuovi Type: GUnixMount default_location=file:///media/packages_orzinuovi themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(4): produzione -> file:///media/produzione Type: GUnixMount default_location=file:///media/produzione themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(5): repository -> file:///media/repository Type: GUnixMount default_location=file:///media/repository themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(6): saga -> file:///media/saga Type: GUnixMount default_location=file:///media/saga themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0 Mount(7): thiene -> file:///media/thiene Type: GUnixMount default_location=file:///media/thiene themed icons: [drive-harddisk] [drive] can_unmount=1 can_eject=0 is_shadowed=0
(In reply to comment #3) > If I execute 'gvfs-mount -li' with GDU 2.30 i receive this error message > > gvfs-mount:10075): GVFS-RemoteVolumeMonitor-WARNING **: invoking List() failed > for type GProxyVolumeMonitorGdu: org.freedesktop.DBus.Error.NoReply: Message > did not receive a reply (timeout by message bus) > > Otherwise if I execute the same command with GDU 2.28 and no difference in > other packages I have this answer : > > (gvfs-mount:10152): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() > failed for remote volume monitor with dbus name > org.gtk.Private.GduVolumeMonitor: > org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process > /usr/lib/gvfs/gvfs-gdu-volume-monitor received signal 11 Looks like your gnome-disk-utility/udisks installation is not working in either 2.28 nor 2.30, so > Volume(0): home_bestione > Type: GUnixVolume that's why gio is falling back to the built-in GVolumeMonitor. I can't explain, however, why the failure mode in 2.28 gives you the GUnixVolumeMonitor but 2.30 doesn't - maybe you can get back to the 2.28 mode by setting GIO_USE_VOLUME_MONITOR=unix (see e.g. http://library.gnome.org/devel/gio/unstable/ch03.html for details) or completely uninstalling gnome-disk-utility. Either way, this is not a gvfs problem, it's a problem with your gnome-disk-utility/udisks installation. Suggest to file this bug with your distribution vendor as setting up udisks is very distro specific and requires careful selection of the versions needed. Closing as NOTGNOME and good luck!
Comment on attachment 158302 [details] This is my fstab (Please pay attention to the mime types as getting the type right will make it easier for people to view it in a browser - the file is obviously text/plain, not application/octet-stream.)