← Back to team overview

nssbackup-team team mailing list archive

[Bug 701403] [NEW] Error "File access manager not initialized" when running as root

 

Public bug reported:

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_PERMISSION_DENIED - Permission denied.]
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/sbackup/sbackup/fs_backend/_gio_utils.py", line 362, in _mount_done_cb
    self.__mount_finish_callback(error)
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_fam.py", line 157, in _mount_cb
    raise exceptions.FileAccessException("Unable to mount: %s" % error)
FileAccessException: Unable to mount: Login dialog cancelled

(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

** Affects: sbackup
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Simple
Backup Maintainers, which is subscribed to Simple Backup.
https://bugs.launchpad.net/bugs/701403

Title:
  Error "File access manager not initialized" when running as root



Follow ups

References