You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Backintime performs the backup,
but when I restart it then says:
"Can't mount 'encfs --extpass=backintime-askpass /media/franco/MyPassport4T/backup-backintime /home/franco/.local/share/backintime/mnt/D9E7F1ED/mountpoint':
Error decoding volume key, password incorrect"
Nevertheless, if then I insert the password in Settings everything keeps working fine.
I have checked 'Cache password for Cron',
and I have tried checking and unchecking 'Save password to keyring'
always the same problem
I have Ubuntu 16.04LTS
The text was updated successfully, but these errors were encountered:
@afrap There is a new forming maintaining team and we do review all issues. Is this problem still relevant for you, can you reproduce it with a newer or the latest release? Did you find a solution?
I could imagine that the used keyring package picks the wrong backend to get the password and it is stored in two "password safes" (one with the wrong password). keyring uses a new ChainingBackend (introduced 2018) which iterates over all installed pw safe backends and may cause this problem IMHO.
If the problem still exists could you please retest with a newer version of BiT (from the package maintainer or via Github).
You can find some instructions to add diagnostic output around keyring ins this issue:
Backintime performs the backup,
but when I restart it then says:
"Can't mount 'encfs --extpass=backintime-askpass /media/franco/MyPassport4T/backup-backintime /home/franco/.local/share/backintime/mnt/D9E7F1ED/mountpoint':
Error decoding volume key, password incorrect"
Nevertheless, if then I insert the password in Settings everything keeps working fine.
I have checked 'Cache password for Cron',
and I have tried checking and unchecking 'Save password to keyring'
always the same problem
I have Ubuntu 16.04LTS
The text was updated successfully, but these errors were encountered: