- This topic has 3 replies, 1 voice, and was last updated May 19-5:34 pm by kempelen.
-
Posts
-
kempelen
Hi all,
For some reason I have two instances of gnome-keyring-daeamon under my user, I think this is not good. The problem I have from this is that if I open “SeaHorse” to see the secret stored data, I don’t see it. I can see only GPG and SSH keys. If I do the following then I have good access to the secret service:
– kill the instance that is with “–start” parameter.
– start it again with –replace instead of –start parameter.Then I have only 1, and SeaHorse displays all data.
$ ps x | grep keyring 1788 ? Sl 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login 3062 ? Sl 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets 3933 pts/3 S+ 0:00 grep keyringThus my question: is this good behavior? If not, what causes this and how to fix?
This is on antiX 26 Full, IceWM, x64. Previously I was using KeePassXC as secret store on antiX 23, but that was “cumbersome”… So far gnome-keyring-deamon is smooth, I just cannot see it from SeaHorse. Yet, programs store and retrieve data correctly.
Thanks in advance!
It’s now worse than I thought, because “digikam” required “kwallet6“. Now Brave Browser wants to create a KDE default keyring, despite it was using my gnome-keyring a few days prior. ProtonMail Bridge is still storing it’s secret data somewhere, but I don’t know where (probably gnome-keyring, because I configured up my “digikam” later than the rest of the system.)
Additionally, starting seahorse from console shows this warning, and I cannot get it anymore show the secret service data, regardless I kill or replace processes, as written above.
(org.gnome.seahorse.Application:30161): seahorse-WARNING **: 11:06:31.939: gkr-backend.vala:94: couldn't connect to secret service: createDLGroup failed: maybe libqca-ossl is missingI do know what secert-service bus has this problem by design, that multiple providers don’t work. So maybe I should let all programs just store wherever they want and hope they will work. 🙂 I hoped that taking out “KeePassXC” from the equation will solve all this problems, but no such luck.
Solved this
1. Some programs need parameter to choose between “kwallet” and “gnome-keyring”.
brave-browser --password-store=gnome-libsecretTo solve that I made a BASH alias for this command. And copied the .desktop file to my ~/.local/share/applications/ and added the parameter to all Exec= lines. Element uses the same parameter.
2. When two gnome-keyring-daemon instances are running, some programs cannot choose
To “solve” that I removed the libpam-gnome-keyring package. Purpose of this was to automatically open the keyring.
That would work as:
– You have a “Login” keyring, that has same password as login password, and contains only the password entry to “Default keyring”
– You have all data in “Default keyring” but don’t need to enter any passwordsSo now I need to enter “Default keyring” password when a program needs the data, but that’s OK.
For some reason ProtonMail Bridge perfectly used the two daemons, other programs (Brave, SeaHorse) do not work with that at all. There is a suspicion that the –login instance that is started by SlimSki via PAM modules starts earlier than D-Bus and then hangs everything. But I cannot fully confirm that, because ProtonMail Bridge worked with that PAM system opened keyring perfectly and automatically (i.e. no password asked).
Solved better
The whole problem was created by ProtonMail Bridge – totally misbehaving on D-Bus and towards the keyring, making it impossible for any other apps to use it.
So probably no other antiX user will run into this, unless they use ProtonMail Bridge. 🙂
Sorry for the noisy post – took me 6-7 hours to debug it (with a lot of help from Claude Code).
2613 ? Sl 0:00 protonmail-bridge 2621 ? Sl 0:00 /usr/lib/protonmail/bridge/bridge-gui --session-id 20260520_001122948 --launcher /usr/lib/protonmail/bridge/proton-bridge 2627 ? Sl 0:00 /usr/lib/protonmail/bridge/bridge --grpc --parent-pid 2621 --launcher /usr/lib/protonmail/bridge/proton-bridge --session-id 20260520_001122948 2640 ? Ss 0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 8 --session 2641 ? Z 0:00 [dbus-daemon] <defunct> 2652 pts/2 R+ 0:00 ps xaSolved by: removing the PAM module libpam-gnome-keyring, which would work perfectly if ProtonMail was not misbehaving horribly. Or maybe I’ll remove proton from autostart and start it before Thunderbird – manually. And then start any well-behaving program first, like for example a dummy search on secret store (in ~/.desktop-session/startup)
sleep 5 && secret-tool search application placeholder &
- You must be logged in to reply to this topic.