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 533565 - SSHfs unmounting
SSHfs unmounting
Status: RESOLVED DUPLICATE of bug 522424
Product: tomboy
Classification: Applications
Component: General
0.10.x
Other Linux
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-17 13:54 UTC by Alexie
Modified: 2008-05-17 14:11 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alexie 2008-05-17 13:54:25 UTC
When Tomboy syncs with a sshfs it doesn't unmount after completion (i think). The result is that if one wishes to resync it fails due to the mounted dir...

umounting solves this issue. Perhaps it is not a bug since in my system I need to sudo umount the sshfs partition...

logfile below, if you need more info, pls ask

many thanks
a

logfile: 
5/17/2008 3:42:20 PM [DEBUG]: SyncThread using SyncServiceAddin: SSH (sshfs FUSE)
5/17/2008 3:42:20 PM [DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 22 alexie@heliconius.cap.ed.ac.uk:/home/alexie/tomboy /home/alexie/.tomboy/sync-sshfs
5/17/2008 3:42:24 PM [DEBUG]: Error calling /usr/bin/sshfs
5/17/2008 3:42:24 PM [DEBUG]: Exception while creating SyncServer: An error ocurred while connecting to the specified server:

fuse: mountpoint is not empty
fuse: if you are sure this is safe, use the 'nonempty' mount option

  at Tomboy.Sync.FuseSyncServiceAddin.MountFuse (Boolean useStoredValues) [0x00000] 
  at Tomboy.Sync.FuseSyncServiceAddin.CreateSyncServer () [0x00000] 
  at Tomboy.Sync.SyncManager.SynchronizationThread () [0x00000]
Comment 1 Sandy Armstrong 2008-05-17 14:11:03 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 522424 ***