-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Save password to keyring" option is disabled #545
Comments
Please make sure |
python-secretstorage 2.1.1-1 and python-gnomekeyring 2.32.0+dfsg-3 are installed but it is still disabled. |
Please post the output of |
|
I am not sure if it is related but it looks related, so I will mention about this just in case. Now when I run BackinTime I get three consecutive error messages: First:
Second:
Thirdly, I see the first message again. Then snapshots of backup set are not loaded. When I create a new profile with local folders, no encryption, I get only the first error message and process suddenly ends, dialogs disappear. In my current main profile;
|
Please install |
Problem solved! Thank you very much. :) |
I have the same problem on Manjaro linux KDE. I've installed python2-secretstorage and python-secretstorage (python3) The following command run fine for both python2 and python3:
How is libcanberra-gtk-module related to the keyring? Is it needed in KDE? In my case "Save password to keyring" is not greyed out, but I cannot check the checkbox when I click on it. I don't know if it's just an artifact of the theme I'm using tough, but it doesn't seem so. |
Well, I keep getting the error messages mentioned by me above from time to time. I got those errors 15 minutes ago and I used that command again, then I changed my backup schedule as "every 5 minutes", then I closed BIT. Now I check and see that BIT took backup according to new schedule. My conclusion: BIT does not apply schedule when this problem (about pw-cache) occurs in background. Update: BIT took only 1 backup in 25 minutes. I run that command again. Now if it will take another backup in a few minutes, I think it means BIT only takes 1 backup after that command, then stops and does not apply the backup schedule anymore. Update 2: No, BIT did not take another backup despite I run that command. Strange. Update 3: I have compiled and updated to v1.1.12. We will see if the problem persists in this latest version. |
@DX486 the schedule |
If I run
and right afterwards a dialog appears asking me the password for SSH (every time). The backend seems to be present, still the checkbox is not clickable. Also if I position the cursor on the field "SSH private key" and I hit tab the next field focused is "Cache Password for Cron...". It seems that the field "Save password to keyring" is somehow disabled or ignored. |
@simgunz could you please manually remove the password from Kwallet, stop pw-cache with |
I can't even find it in KWallet. Under which name/category should the password be stored? |
I've also tried to create a new SSH profile, and also in that case the checkbox cannot be checked. |
@simgunz I'll make myself a Manjaro VM and test it. Sounds like a bigger problem. |
Thanks to look into this. |
Hi. Just wanted to add that the Problem appears in plain archlinux as well (Using latest KF5/Plasma5). My SSH Key is in the ssh-agent, connecting to the server from the terminal works like expected, no password for the key needed. Starting backintime-qt4 --debug in the same terminal gives me the above output (with password available: true). |
Just a note: I don't have any problem since I've upgraded BIT to v1.1.12 (on debian 8.3 stable). |
I'm actually running v1.1.12 |
Okay, there was a logic error with the |
I'm glad you've already found the problem! Thanks |
I can confirm that the patch works. I also mentioned it in the according bug in the python-keyring bugtracker: jaraco/keyring#168 |
The problem seems to be solved now, using python-keyring 8.5.1 |
Thanks for the feedback. I'll close this bug as it was no bug in BIT. |
I need to ask your support again on this issue, because it's happening again. The debug output I'm getting is the same as above, and the checkbox is disabled so that I cannot save the SSH password. I'm using backintime 1.1.12 and python-keyring 9.0
|
I backported the patch for 1.1.12 and asked the package maintainer for the AUR package to include it. Should be fixed soon... |
Updated in backintime 1.1.12-4 |
Ok. Sorry, I reported it again because I remember it was already fixed on my system, so I thought it broke again. While the patch was not yet there, so maybe I remember wrong. In any case I've tested the AUR package today, and it works correctly. Thanks again |
No worries, mate |
I'm having this issue using version 1.2.0~alpha0 on Gentoo. Then backintime stopped working properly by complaining about being unable to access the password, so I removed it manually from kwallet, expecting to be asked for it again. Now Backintime is working again, but the "Save password to keyring" option is disabled. I also tried re-installing Backintime (also removing ~/.config/backintime and ~/.local/share/backintime), but it still doesn't work.
doesn't show anything that seems to be out of the ordinary...
|
"Save password to keyring" option is disabled. What can be the reason?
Cache password option is enabled but I am asked to enter the password again on every backup.
I use debian 8.3. BackinTime 1.0.36-1. Seahorse 3.14.0 is installed.
The text was updated successfully, but these errors were encountered: