sbackup is not able to mount remote directory via SSH (testing works fine)

Thank you for using SBackup and for taking the time reporting this bug.

In order to track down the cause of the problem some more information are required. Please answer the following questions:

* what distribution do you use?
* from where was it installed (PPA, from source)?
* Is the bug reproducible; does it happen every time?
* do you run sbackup as superuser (root) or as regular user?
* are you able to open your backup destination using Nautilus/command line?

At first glance, your specific error looks like an underlying problem with GIO/GVFS to me not directly caused by SBackup.

Thanks for your help.

Hi,

thanks for the fast reply. Below the answers to your questions:

* I am using Kubuntu 10.04 (all available updates installed)
* sbackup was installed from ppa:
$ aptitude show sbackup
Paket: sbackup
Zustand: Installiert
Automatisch installiert: nein
Version: 0.11.2ppa1~lucid1
Priorität: optional
Bereich: admin
Verwalter: Simple Backup Maintainers <email address hidden>
...
* yes, it is reproducible
* I am running it as superuser to enable backup of all userdata and some other stuff only available for root. I am starting it with command "sudo sbackup-config-gtk"
* yes, I am able to mount the destination using KDEs dolphin file manager (network -> add network folder -> ssh ..... ). In addition as already written above when configuring sbackup the wizard is able to mount the network folder, only when performing the real backup the mount process fails by some reason.

I hope I can try it with another machine soon to check if it is a local problem on the used laptop or not.

Thanks, Andreas

> I hope I can try it with another machine soon to check if it is a local problem on the used laptop or not.
Any progress on this?

Sorry for the delay. I was on vacation on short notice, so retesting was not possible for a while.

Today I checked on another machine (also an Kubuntu 10.04 with updated sbackup 0.11.3). I was able to reproduce the problem. While trying to find the error I used both fuse and gio backend for testing, which both failed.

But for some reason it seems like the backup process is running fine when starting just by typing "sudo sbackup". The backup is running at the moment and data appears on remote host. So it looks like that root cause for my problems is somehow related to the "backup now" button on GUI. Maybe this is calling the sbackup daemon with wrong/incomplete parameters?

BR, Andreas

Did you tried to make an sudo ssh to the server?

Yes, I tried "sudo ssh" before without problems. So the rootcause should be somewhere else.

But I can present good news: I just did a retest after upgrading my Kubuntu systems to maverick (10.10). By some reasons the problem is now solved. Thanks a lot for all the hints.

I get this error now in 0.11.6 on Ubuntu Precise (12.04), but not with 0.11.4 (same config, same backup server, same laptop etc.)
0.11.4 is what is in the Precise repo at Ubuntu, 0.11.6 I just grabbed from launcpad download. There, it sais 'Debian Wheezy', is that related to the problem?

(I don't see any .deb downloads for earlier versions...?)

After some further testing, I now see the problem is different. Backups *do* work, for both versions.
But from the config or restore window, acces to the remote machine *does not* work. It did use to work at least in 0.11.4 about a month or two ago (last used).
I've seen some bug reports (not sbackup) related to gvfsd not working/connecting for the root user that give the same symptoms ('volume doesn't implement mount')...