After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 400001 - Cannot mount sshfs filesystems
Cannot mount sshfs filesystems
Status: RESOLVED INCOMPLETE
Product: gnome-vfs
Classification: Deprecated
Component: Volume and drive handling
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-23 23:07 UTC by Sven Arvidsson
Modified: 2010-05-14 10:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Sven Arvidsson 2007-01-23 23:07:23 UTC
This bug was filed in the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=393508

"I have several sshfs entries in my /etc/fstab. I can mount them with no
problems from the command line. If I try the same with Nautilus, it
does not work. For the ones that require passwords, a popup asking for
it does come up, but then it does nothing at all. For the ones that
don't require a password, nothing happens.

Other filesystems like NFS work just fine. I've tried sshfs with
different machines, and it always work from the command line."
Comment 1 Christian Kirbach 2007-01-27 22:38:19 UTC
With Places->Connect to server, you can use nautilus to navigate remote ssh folders natively via gnome-vfs

Don't have the time now  to check with an sshfs fstab entry

Comment 2 Sven Arvidsson 2007-01-30 16:22:12 UTC
I can reproduce this in 2.16, both with Nautilus and with the drivemount applet. 
Comment 3 Vincent Untz 2007-02-20 16:06:51 UTC
Looks like a gnome-vfs issue.
Comment 4 _FrnchFrgg_ 2007-04-09 18:36:58 UTC
I think this is related to bug 397441 that I filed some time ago (probably against the wrong component). To summarize what I said there, it seems that the sshfs program is killed as soon as nautilus (or gnome-vfs) is given back the control; protecting sshfs with screen (the simplest hack I could find to test) works around the problem.
Comment 5 Yann Rouillard 2007-11-01 01:39:11 UTC
I am also able to reproduce this bug.
I straced the mount process and it seems ssh receive a SIGHUP signal at some time and hence close the connection.
As the connection is closed, sshfs automatically unmount.

I don't understand why and who a SIGHUP is sent, this doesn't happen when you mount from the command line.

The bug has also been reported on Ubuntu: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/158973


@_FrnchFrgg_, I think you're right, Bug 397441 is a dup of this one.
Comment 6 Yann Rouillard 2007-11-01 02:13:26 UTC
I suppose this happens because gnomevfs launches the mount command in a pty using the gnome_vfs_pty_open function. As soon as the pty is closed, the SIGHUP signal is sent and sshfs is umounted.
Comment 7 André Klapper 2010-03-27 17:08:22 UTC
gnome-vfs is not actively developed anymore and has been replaced by gvfs.
Is this still a problem in a recent GNOME version (2.28 or 2.30) which uses gvfs?

If this is still an issue for gvfs please file a new bug report against gvfs with good steps to reproduce, or move this existing report to the product gvfs.
If this is not an issue anymore in a recent GNOME version, please close this report as RESOLVED OBSOLETE.
Comment 8 Tobias Mueller 2010-05-14 10:13:07 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!