> DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found. > 'keyring.backends.chainer' can't be used with BackInTime > ... > Two Conclusion: > 1) Backintime fails to access the keyring when keyring.backends.chainer is in > use.
Correct. The keyring.backends.chainer.chainerBackend is not yet supported in BiT and perhaps never will be because it iterates over all installed backends and picks the "best one" by some internal logic. The chosen backend my not be the one where the users saves the credentials anyhow. So a decent fix for this would be to add a settings GUI to BiT so that the user can choose which backend is the right one (containing the credentials). I have documented future implementation options in this issue comment: https://github.com/bit-team/backintime/issues/1321#issuecomment-1271689827 > With python3-keyring 22.0.1-1 backintime succeeds to read the ssh password > However logs now say: > DEBUG: [common/tools.py:823 keyringSupported] No appropriate keyring found. > 'keyring.backends.SecretService' can't be used with BackInTime > ... > Two Conclusion: > ... > 2) Backintime's test for keyring back ends does not work properly. > It does not recognize a back end as functional it does work with later on. Correct. I think this has the same reason as the bug #1321 linked in above issue. I am preparing a fix for this bug (but NOT adding support for the ChainerBackend!) and hopefully attach a patch for this if the package maintainer really wants to backport this to BiT v1.2.1 (with no support from the BiT team I guess since we are preparing a new stabilized release 1.3.x where many bugs are fixed but no new features are added (therefore "stabilize" ;-) So I'd prefer if the package maintainer waited for stabilized BiT version and packages the new BiT version we are working on.
