-
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
Suddenly BIT can't unlock SSH key any more #1025
Comments
Executing the following commands seems to have solved the SSH key unlock problem:
Nevertheless it would be useful to know what happened and why... as I said, it happened all of a sudden without any apparent reason. Maybe the last command would have been enough to solve the problem? If so, doesn't a system reboot do the same (i.e. "stop the password cache")? Tomorrow I'll check for the second problem (cannot save job settings because of the maximum command line length problem). |
The second problem persists, I opened #1027 for it. |
Seems to me we can close this issue because it is kind of a duplicate? |
Actually this remains a mystery: the error on settings save is indeed #1027, but the original problem is still unexplained. Nevertheless I don't know whether anything can be done right now, unless you have an idea of what could have happened. |
I have just checked your debug output for indicators of well-known keyring and d-bus issues with BiT but couldn't find any. The key problem (reported in the logs) is a D-Bus connection error (and interestingly a double-free or free-of-wrong-pointer error as subsequent error). I could only guess about the reasons (perhaps a new security policy was activated via an update by using Wayland instead of X11, a broken update/installation, an API breaking change in a package/library...). If it is not reproducible anymore I'd suggest to close this issue (and open a new one if it happens again). |
@mauromol Do you think we can close this? |
Since it's impossible to reproduce right now, I think the only reasonable action for this by now is to close. |
I have been running BIT successfully for some YEARS.
Today scheduled backups can't unlock the SSH key any more. I already tried to restart the system and still having this problem.
I'm running Linux Mint KDE 18.3 (based on Ubuntu 16.04). Running BIT 1.2.0.
Here is what gets printed into /var/log/syslog:
So, I thought it could be a good idea to edit my backup profile settings and try to remove/readd the options related to SSH private key password saving. However, whenever I try to click "OK" after editing the settings of this backup profile I now get the following error:
net.launchpad.backintime.LimitExceeded: Maximum length of command line reached (100)
This is a remote SSH backup profile. Let me know if you need further details. Probably I never edited and saved settings for this profile with BIT 1.2.0, but for sure it did work with older versions.
The text was updated successfully, but these errors were encountered: