Unable to use remote target without giving a password
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
sbackup | Status tracked in Trunk | |||||
0.11 |
Fix Released
|
Low
|
Jean-Peer Lorenz | |||
Trunk |
Fix Released
|
Low
|
Jean-Peer Lorenz | |||
sbackup (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Recently in sbackup (I believe since the re-merge with nssbackup), I cannot backup as root. Backups as user still work (and I can open the backup location in nautilus as user). Nothing has changed on the remote machine (backup over ssh). I can 'sudo ssh user@host' without password. Also all required gvfs packages are present (as per bug #617473).
When I press 'Connect' in the 'Set remote target' dialog, I get the error 'Unable to mount host. Login dialogue cancelled'.
When I press 'Make backup now', I get the error 'An error occurred. File access manager not initialized'. No backup is made.
The relevant part of the sbackup log seems to be:
2011-01-11 10:27:54,450 - INFO: Initializing GIO File Access Manager.
2011-01-11 10:27:54,504 - ERROR: Error in `_do_mount`: Login dialog cancelled [ERROR_
2011-01-11 10:27:54,543 - ERROR: Uncaught exception: Unable to mount: Login dialog cancelled
2011-01-11 10:27:54,543 - ERROR: Traceback (most recent call last):
File "/usr/share/
self.
File "/usr/share/
raise exceptions.
FileAccessExcep
(full log attached)
I'm running on Ubuntu Maverick (10.10) 2.6.35-24-generic x86_64
sbackup 0.11.3ubuntu1
gvfs* 1.6.4-0ubuntu1
Related branches
summary: |
- Error "File access manager not initialized" when running as root + Unable to use remote target without giving a password |
Changed in sbackup: | |
assignee: | nobody → Jean-Peer Lorenz (peer.loz) |
importance: | Undecided → Low |
milestone: | none → 0.11.4 |
status: | New → Confirmed |
Changed in sbackup (Ubuntu): | |
status: | New → Confirmed |
Changed in sbackup (Ubuntu): | |
status: | Confirmed → In Progress |
I run also Ubuntu Maverick (10.10) 2.6.35-24-generic x86_64 and have exactly the same problem with sbackup, otherwise a great piece of software. I investigated the log files (with debug log level) and saw the same entries. Today, January 12, 2010 I installed an update of sbackup and now I have version 0.11.3ubuntu1. Unfortunately, the problem persists.
Regards,
Philip