Comment 11 for bug 1923727

So we already "do it along the same lines" :-)

For issue #2 - I've fixed my local problem

I indeed had kwalletd (the daemon) installed along the default gnome-keyring-dameon.
Both implement a compatible API.

When python.keyring wants a key it iterates all backends - if it finds it in any it uses that data.
## ^^ here the snapped version fails ^^ ##

But if it didn't find any it will try to create a new keystore.
That this happens to prefer kdewallet is a bug that I'll file upstream.
Internally there is a priority system and gnome has 5 which is above the 4.9 of kde.

With the help of our Desktop Team I've found that as workaround one can set this.

$ cat /home/paelzer/.local/share/python_keyring/keyringrc.cfg
[backend]
default-keyring=keyring.backends.SecretService.Keyring

This is because both still use different endpoints, that might there be version dependent as IIRC they want both to implement this.
That will make sure the gnome keyring is used, and not kwallet.

Now with my local setup sorted out and via config hard-set to prefer the gnome-keyring the git-ubuntu side of this gets even more interesting -- see next bug update ...