BIT Gnome "Could not unlock ssh private key. Wrong ..."

Do you use latest version from AUR? 1.0.36-3 at time of writing?

Dependencies are python2-keyring, python2-secretstorage and/or python2-gnomekeyring

If you activated 'Save Password to keyring' please check if it is set in Gnome Keyring (seahorse).

Also please try if 'backintime --pw-cache stop' and 'backintime --pw-cache start' will fix this.

Regards,
Germar

Hey Germar,
thanks, yes, version is the latest.
Dependencies are all installed.
'Save Password to keyring' wasn't checked (and the box is disabled, perhaps there is a problem?)
Seahorse has only one entry which is my openSSH id_rsa key.

-- pw-cache stop fails with: ERROR: [Password_Cache.Daemon.stop] pidfile /home/dirk/.local/share/backintime/password_cache/PID does not exist. Daemon not running?

--pw-cache start has no specific output, but also don't fix the problem.

Regards,
Dirk

If you start BIT from commandline is there a warning 'import keyring failed'?

Please post the output of 'python2 -c "import keyring; print keyring.get_keyring()" '
and 'ssh-agent'

Here comes the output:

[dirk@i7-arch-host ~ $] backintime

Back In Time
Version: 1.0.36

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

[dirk@i7-arch-host ~ $] backintime-gnome

Back In Time
Version: 1.0.36

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime-gnome --license' for details.

/tmp/backintime/i7-arch-host/dirk/1 does not exist

>>>>> GUI is runnning now, missing path is only a test profile

[dirk@i7-arch-host ~ $] python2 -c "import keyring; print keyring.get_keyring()"
<keyring.backends.Gnome.Keyring object at 0x7fbe8f4c3d10>

[dirk@i7-arch-host ~ $] ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-icLxkfKSyact/agent.3066; export SSH_AUTH_SOCK;
SSH_AGENT_PID=3067; export SSH_AGENT_PID;
echo Agent pid 3067;

If it helps you, I cloud also add you in jabber.

That all looks fine. So the problem is not the keyring nor ssh-agent.

Do you use some very special chars in the password? Could you please try to use an easy password or even no password at all? (Your connection will still have the same security. This password is only to secure your private key. As long as this key doesn't get into wrong hands you're fine.)

Feel free to contact me on jabber.

This problem is fixed in 1.0.40