No backup created when allowing GNOME to prompt for password

[IMSargon]

Linux Distro: Ubuntu Intrepid Ibex Beta, all current updates
SBackup Version as reported by Synaptic: 0.10.5ubuntu2
SBackup Version as reported by About Box: 0.10.4

This problem seems to effect regular ssh configurations where the password is not provided as part of the remote directory, or configurations where the private key requires a password to unlock.

"ssh://test@localhost/home/test/files/"
Under such configurations, a remote directory like the one above is entered. Clicking "Test" brings up the GNOME "Authentication Required" box, into which the password is entered. A green checkmark appears by the path. Clicking "Backup Now!" brings up the "A backup run is initiatied...." box, but no backup is actually created.

I do wish to be prompted for a password under these circumstances. I have been successful with both entering the password in the path and using a passwordless ssh key, but neither is the solution I'm looking for. The expected result would be either some sort of error or a backup actually being created.

[Martin Schaaf (mascha)]

The gnome authentication isn't initialized by sbackupd.py

[Martin Schaaf (mascha)]

Please can you try the linked branch and say me if it fixes your issue.

[IMSargon (imsargon)]

If I save my configuration and then execute sbackupd.py, it is able to create a backup in the appropriate directory.

However, if I use simple-backup-config.py (which now shows the correct version 0.10.5) it behaves just as before, prompting for the password when checking the directory, green-checking the directory, but failing when using the "Backup Now!" button, despite the pop-up that says it's working in the background.

[Martin Schaaf (mascha)]

How did you install this version? Did you checked out the branch and startet simle-backup-config.py from the checked out directory? If you call simple-backup-config.py from the checked out place it will call /usr/sbin/sbackupd and not the one from the current dir.

Be sure do overwrite sbackupd.py in /usr/share/sbackup with the new version but before create a backup from the old file. Then run simple-backup-config. Sorry for not beeing more clear in the first place. Thank you for your help.

[IMSargon (imsargon)]

I had used "make install" to install the software, and then changed my menu entry to point to the newly installed version (in /usr/local/sbin/ instead of /usr/sbin/).

Now, I have copied the new "sbackupd.py" into my "/usr/share/sbackup/" directory, renaming the old version as you recommended. I am now prompted once when checking the directory, and again when clicking "Backup Now!" after which the backup successfully completes. Excellent. This is the expected behavior.

Thank you for your help. This will be a well-received update for GNOME users. I might mention that the Authentication dialog hangs around until the backup process completes. This is a minor cosmetic issue, however. Do you have a guess as to how long it takes for a patch like this to get from you to the Ubuntu repositories?

[Martin Schaaf (mascha)]

> This will be a well-received update for GNOME users. I might mention that the Authentication dialog hangs
> around until the backup process completes. This is a minor cosmetic issue, however. Do you have a guess as
> to how long it takes for a patch like this to get from you to the Ubuntu repositories?

I do not know how long it will take. I started working on it because I was also annoyed by all the existing bugs that have patches and that aren't committed. So I startet my own branch to help the maintainer to create a new release. Please ask him too for a new release and possibly it helps to use the "Nominate for release" button on this site.