[Desktop-packages] [Bug 223636] Re: gvfs should unmount remote mounts on network disconnect
See also : https://bugs.launchpad.net/ubuntu/+source/gnome- vfs/+bug/905497 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/223636 Title: gvfs should unmount remote mounts on network disconnect Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs Problem: gvfs does not unmount remote shares if network disconnects. It leads to unusable mounts on my desktop after network is reconnected. Expected behavior: unmount all remote shares on network disconnect Workaround: manually unmount remote mounts before trying to access them after network disconnect/reconnect. It is especially painful for roaming laptop users who always connect to different networks but want to access the same ftp/sftp/etc. server. $ dpkg -l | grep gvfs| cat ii gvfs 0.2.3-0ubuntu4 userspace virtual filesystem - server ii gvfs-backends 0.2.3-0ubuntu4 userspace virtual filesystem - backends ii gvfs-bin 0.2.3-0ubuntu4 userspace virtual filesystem - binaries ii gvfs-fuse 0.2.3-0ubuntu4 userspace virtual filesystem - fuse server ii libgvfscommon0 0.2.3-0ubuntu4 userspace virtual filesystem - library $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/223636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 223636] Re: gvfs should unmount remote mounts on network disconnect
For users who use gvfs exclusively in a desktop environment: This kind of issue is apparently somewhat addressed by a program called Gigolo (http://www.uvena.de/gigolo/index.html) It makes it easier for me to do the reconnecting. More specifically, it doesn't care if the mount was left dangling; it's smart enough to sort that out simply by being asked to connect. As for those who might be using gvfs to support CLI operations... maybe Gigolo's source code can reveal some potentially useful insights that can be carried into gvfs... http://git.xfce.org/apps/gigolo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/223636 Title: gvfs should unmount remote mounts on network disconnect Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: gvfs Problem: gvfs does not unmount remote shares if network disconnects. It leads to unusable mounts on my desktop after network is reconnected. Expected behavior: unmount all remote shares on network disconnect Workaround: manually unmount remote mounts before trying to access them after network disconnect/reconnect. It is especially painful for roaming laptop users who always connect to different networks but want to access the same ftp/sftp/etc. server. $ dpkg -l | grep gvfs| cat ii gvfs 0.2.3-0ubuntu4 userspace virtual filesystem - server ii gvfs-backends 0.2.3-0ubuntu4 userspace virtual filesystem - backends ii gvfs-bin 0.2.3-0ubuntu4 userspace virtual filesystem - binaries ii gvfs-fuse 0.2.3-0ubuntu4 userspace virtual filesystem - fuse server ii libgvfscommon0 0.2.3-0ubuntu4 userspace virtual filesystem - library $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04" To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/223636/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 905497] Re: gvfs should auto reconnect when disconnected
For users who use gvfs exclusively in a desktop environment: This kind of issue is apparently somewhat addressed by a program called Gigolo (http://www.uvena.de/gigolo/index.html) It makes it easier for me to do the reconnecting. More specifically, it doesn't care if the mount was left dangling; it's smart enough to sort that out simply by being asked to connect. As for those who might be using gvfs to support CLI operations... maybe Gigolo's source code can reveal some potentially useful insights that can be carried into gvfs... http://git.xfce.org/apps/gigolo See also : https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/223636 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs in Ubuntu. https://bugs.launchpad.net/bugs/905497 Title: gvfs should auto reconnect when disconnected Status in “gnome-vfs” package in Ubuntu: Confirmed Bug description: When a connection is made to a remote server through, for example ftp, in many cases the host disconnects when there is no activity during a timeout. This is not a particular problem is Nautilus, because then a reconnect will take place. However, when a file is opened on the remote server (for example a text file opened by gedit) and when a disconnect has taken place, saving the file results in an error. gvfs should detect this situation and automatically reconnect. Woraround for this situation: navigate with Nautilus to the remote connection, press F5 for refresh and the connection is re-established. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/905497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 212789] Re: gvfs fuse mount is not functional after logout and subsequent login
Leveraging off oyvinst's script (comment #14)... I worked around this bug by doing a little bit more: # Quick and dirty hack to unmount ~/.gvfs directory on logout. if test -d "$HOME/.gvfs" ; then for f in "$HOME/.gvfs" do /bin/fusermount -zu "$HOME/.gvfs/$f" 1>/dev/null 2>&1 || true done /bin/fusermount -zu "$HOME/.gvfs" 1>/dev/null 2>&1 || true rmdir "$HOME/.gvfs" fi ... the script's written from gut-feeling and I didn't actually go through the steps to troubleshoot any bugs in its logic... >_> I applied this for Ubuntu 11.10 ... my quickfix intuition is that the .gvfs folder should be recreated from scratch on session login for the gvfs magic to work, even after doing the initial unmount... If someone could instead point out what command(s) are used to do the magic service's initialization, we might be able to "restart" it within a session instead of cycling through "logout -> login". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/212789 Title: gvfs fuse mount is not functional after logout and subsequent login Status in GVFS: Fix Released Status in “gvfs” package in Ubuntu: Fix Released Status in “gvfs” source package in Hardy: Fix Released Status in “gvfs” package in Debian: New Bug description: Binary package hint: gvfs GVFS-backed mounts are working perfectly on fresh OS boot. After logout and following login every attempt to access $HOME/.gvfs (i.e. with ls or df) results in 'Transport endpoint is not connected' error message. At the same time $HOME/.gvfs is present in /etc/mtab. Also GVFS-mounts are accessible through FUSE when /usr/lib/gvfs/gvfs-fuse- daemon is called with some other directory as argument. Branch of Ubuntu involved is hardy (with all current updates installed), version of gvfs, gvfs-backends, gvfs-fuse and libgvfscommon0 packages is 0.2.2svn20080403-0ubuntu1. TESTCASE: - log into GNOME - browse a network location using nautilus - verify that the location is fuse mounted under .gvfs - close your session - switch to a vt and look to .gvfs or log again and do that, you should get an error saying that .gvfs is not connected - install the update - try those again, now .gvfs is correctly unmounted on logout, and on next login it's still usuable To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/212789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp