the plugin shouldn't display the gvfs-fuse-daemon "file-system", it should be blacklisted at all time. currently it's possible to hide it by going into Properties>File systems>Exclude specific file systems and add gvfs-fuse-daemon.
I dont have a system where gvfs-fuse-daemon works, so can you paste me the corresponding lines of etc/fstab + etc/mtab so that i see how to blacklist it ? you can have a look at devices.c:disks_refresh(). Maybe only removing the match on 'fuse' there and in disks_classify/disks_new should do the trick.
Created attachment 4320 [PATCH] git-format-patch Attached is a patch that blacklists gvfs-fuse-daemon. PS: here is the line as displayed by mtab: gvfs-fuse-daemon on /home/m8t/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
You mean that you don't see individual gvfs mounts, but only a single mount on .gvfs ? That's ugly.. if there were separate mounts that would have been interesting to show them, but if it's that way.. i suppose the df output for this mountpoint is useless too ? (ie doesn't display remote disk free by gvfs mount..)
Applied in http://git.xfce.org/panel-plugins/xfce4-mount-plugin/commit/?id=c64f383ef3d205b1311f114bcef0933ba3bc332c
(In reply to comment #3) > You mean that you don't see individual gvfs mounts, but only a single mount > on .gvfs ? That's ugly.. if there were separate mounts that would have been > interesting to show them, but if it's that way.. i suppose the df output for > this mountpoint is useless too ? (ie doesn't display remote disk free by > gvfs mount..) Individual Gvfs mounts can only be displayed with "gvfs-mount --list", they never appear with the command "mount" (neither does "df"). Marking this bug as CLOSED :)
CAn you please argue on why this should be blacklisted? IMHO the plugin should list nearly everything; very similar to mount and df. So I am strongly in favor of removing this patch and leaving the user the choice to hide gvfs-fuse-daemon. I also had it blacklisted manually, that worked fine, and that's the purpose thereof. Thanks for consideration.
I'll let mike argue (cause i dont have an opinion, not having gvfs-fuse-daemon), but i think the rationale is hiding useless mountpoints. In that case, it's of no interest to show it, since it doesnt give information, nor manual mounting/umounting does what the user want, ie mount/unmount gvfs mounts, which should be adressed by directly talking to gvfs and would be a completely different issue ?. The plugin already 'whitelists' based on fs type/device path after all....
(In reply to comment #6) > CAn you please argue on why this should be blacklisted? IMHO the plugin > should list nearly everything; very similar to mount and df. > > So I am strongly in favor of removing this patch and leaving the user the > choice to hide gvfs-fuse-daemon. I also had it blacklisted manually, that > worked fine, and that's the purpose thereof. > > Thanks for consideration. As written, individual Gvfs mounts aren't displayed by the plugin, and the mounpoint "gvfs-fuse-daemon" doesn't make sense to be kept around. You can run the command "fusermount -u $HOME/.gvfs" to unmount the mount point, but that is clearly not wished either. No one should mess around with the process "gvfs-fuse-daemon". The "gvfs-fuse-daemon" process allows you to browse mounted file systems inside "~/.gvfs". That's it. For being able to unmount mount points created with "gvfs-mount", the plugin should support "gvfs" anyway. Now I had like to stop arguing there. If you think there is a valid point to have an unuseful entry in the plugin, just give an argument in that direction, and not the other way around.