Thanks.
But the merit actually goes to a chap going by the handle Bentolor.

He posted about this same issue* back in 2019 and came up with the keyringrc.cfg file for setting the backend.
See https://github.com/jaraco/keyring/issues/391

* BiT fails because it cannot make sense of the ChainerBackend

A chap going by the handle Jaraco (autor of keyring?) explains the process further down.
You may want to give it a read, it may at some point be useful to you.

Best,

A.

No so fast ...

A deeper look helped me understand something that should have been pointed out to users in a clear(er) manner.
ie: for the half baked hoi-poloi like me.

The problem was that BiT did not automagically choose the available backend to use, seems that getting that done is a rather complex matter.
The solution is an option to add to the BiT GUI, apparently a work in progress to be included upstream, maybe in the next release (?).

But there was a quick, clean and easy alternative: to set it up manually, ending the bloody problem in 5'.
Could not have been easier but ...

Anyhow, if someone else comes across this same problem, the solution is within the BiT FAQs.

TL:DR

Once done, you should get something like this ...

$ python3 -c "import keyring.util.platform_; print(keyring.get_keyring().__module__)"
keyring.backends.chainer
$ 

@greenjeans:
That nails it, no more gnome-keyring in my system ...

$ apt list | grep installed | grep gnome-keyring 
--- snip ---
$ 

... and just the necessary keyrings:

$ 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]
$ 

Edit:
Just an update to confirm that BiT ran this morning's (05/08/25) daily cronjob without any issues.

Best,

A.

And so it seems:
---------------------------------------------
Debian Bug report logs - #998105
backintime-qt: Fails to access the keyring with python3-keyring 23.2.0-1
https://bugs.debian.org/cgi-bin/bugrepo … bug=998105
---------------------------------------------

BiT should be able to work properly without gnome-keyring or keepassxc installed.

The problem seems to be (?) with how BiT looks for and finds (or not) a keyring to use.
For whatever reason, it does not find and select the installed python3-keyring, going for whatever else is available to use.

Which is why, instead of using the installed python3-keyring 23.9.3-2, it uses the installed (and otherwise unnecessary) gnome-keyring 42.1-1+b2.
Failing to run if I purge it.

Apparently there is/was (?) a patch but the bottom line is that (two years on)  the bug is still present in backintime-qt 1.3.3-4.

So much for my getting rid of all the gnome crap ...

Best,

A.

No. 8^°
What I am saying is this:

ie: a statement of fact.

But further on (for clarity) I should have written this:

Sorry for being ambiguous, my command of the English language is rather lacking.

That said, the only reason (I can come up with) is that BiT looks for a PW and does not find one.

Thanks for your input.

Best,

A.

Just FYI for the database though, I found that Exaile requires not the keyring itself, but the presence of the pkcs package for Exaile to be able to stream internet radio. And this is one of the reasons I am creating a music app of my own to replace it.

I guess (would have to purge gnome-keychain to verify) that it does not find the password to be able to do its job.

From what I gather, BiT is a user mode backup so it only does backup/restore operations on directories where the user has write access.
As it runs automatically (cron job) it needs the password which is (?) in the gnome-keyring.

Thanks for your input.

Best,

A.

BiT will not run properly.

Can you expand on that? What seems to be broken?

Interesting.

I have it installed in my system because BackInTime recommends it.
It is a remnant of the time when I did not block recommended packages.

$ aptitude why gnome-keyring
i   backintime-common     Depends    python3-keyring                                       
i A python3-keyring       Depends    python3-secretstorage (>= 3.2)                        
i A python3-secretstorage Recommends gnome-keyring | libkf5wallet-bin (>= 5.97) | keepassxc
$ 

But I don't use it to store passwords, not at all comfortable with that.

But it happens that gnome-keyring is not a dependency for BackInTime but if I purge it, BiT will not run properly.
keepassxc is not a dependency either and it requires network access, so that would be a hard no for me.

See https://packages.debian.org/en/sid/backintime-common

It would seem (?) that BiT should be using python3-keyring instead of gnome-keyring for me to be able to purge it.

Any ideas on how to get that done?

Thanks in advance.

Best,

A.

It looks like the people who setup Peppermint OS did something different. It is possible to get Chrome to run on XFCE by entering a password for the keyring. What do you suppose they did differently?