Hello: sawbonaï¼ gmx.net wrote: > ... issue I have posted *may* be related to that bug report. Yes, it is.
@c.buhtz Thanks for the link to the FAQs. For some reason I thought the problem at hand was of a murkier nature (incompatibility between packages or similar) but it turned out to be quite simple: BiT did not *automagically* choose the available backend to use. It seems that getting that done is a rather complex matter so the solution is to add an option for that to the BiT GUI. That is still a work in progress to be included in the next (?) upstream release. As is usual in a Linux environment, there was a quick, clean and easy alternative: set it up manually, ending the bloody problem in 5'. Could not have been easier. If someone else comes across this same problem, the solution is within the BiT FAQs: <https://github.com/bit-team/backintime/blob/dev/FAQ.md#problems-errors--solutions> TL:DR backintime FAQs wrote: > To diagnose and solve this follow these steps in a terminal: > # Show default backend > python3 -c "import keyring.util.platform_; print(keyring.get_keyring().__module__)" > # List available backends: > keyring --list-backends > # Find out the config file folder: > python3 -c "import keyring.util.platform_; print(keyring.util.platform_.config_root())" > # Create a config file named "keyringrc.cfg" in this folder with one of the available backends (listed above) > [backend] > default-keyring=keyring.backends.kwallet.DBusKeyring As I make it a point to comment generated / modified *.conf files, I found that I *already* had a "keyringrc.cfg" file in my system. I had generated it back in 03/2021 because (the same problem?) of <https://github.com/jaraco/keyring/issues/391>. ie: backintime fails because it cannot make sense of the ChainerBackend <--- * quoting OP by Bentolor Once done, you should get something like this: [code] $ python3 -c "import keyring.util.platform_; print(keyring.get_keyring().__module__)" keyring.backends.chainer $ [code] I have purged gnome-keyring and have only the *necessary* keyrings: [code] $ apt list | grep installed | grep keyring --- snip --- debian-archive-keyring/stable,stable,now 2023.3+deb12u2 all [installed] devuan-keyring/stable,stable,now 2023.05.28 all [installed] python3-keyring/stable,stable,now 23.9.3-2 all [installed,automatic] $ [/code] BiT seems to work properly / as expected (manually generated snapshot), will report back if anything is amiss. Thank you very much for your input. Best, A. _______________________________________________ Bit-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3//lists/bit-dev.python.org Member address: [email protected]
