Arch Linux

I don't understand why this is not affecting more users. What is special about your system that makes this necessary?

Yeah, Seahorse works fine for me.

My system is nearly out of the Box. The problem occured just one day and then i found the linked issue. But if i'm the only one with this issue here this Bugreport can be closed.

I installed a new arch system.
In gnome and cinnamon my google-chrome started very slowly and the nextcloud client frequently lost its login. Other apps started slow aswell.

I tracked it down to be a gnome-keyring issue. Killing the gnome-keyring-daemon made everything fast, but chrome requests to open the keyring itself.

These commands from the issue solved my problems, my apps start fine again after logging in again:
sudo setcap -r /usr/bin/gnome-keyring-3
sudo setcap -r /usr/bin/gnome-keyring-daemon

I know it works for you, but I see it as my duty to report my problems, because I think multiple users may be affected.
I freshly set up a new laptop. Maybe the capabilty is set only on new installations?
This issue is very hard to track down. I feel like there are a lot of people not having a clue what is causing their issues.

@Richie2, thanks for the info but there is not enough detail. We need *exact* replication steps to recreate the problem.

tl;dr -> "solved" temporarily like this: compile with `--without-libcap-ng', remove the install file, and start the daemon in `.xinitrc` with `eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)`

This is definitely affecting me. Something is broken. I filed a bug when the issue first crept up https://bugs.archlinux.org/task/74037
After upgrading to the latest versions of both `gnome-keyring` and `glib2` , couldn't get `gnome-keyring-daemon` to respond.

I then compiled it with the `--without-libcap-ng` which used to fix it but it wasn't enough today. I noticed that I had to also disable the socket (enabled via the install file.) Then, experimenting with starting the daemon manually on the cli (cf man gnome-keyring-daemon), it started and responded., bringing up the dialog box to insert password to unlock the keyring, etc.
`secret-tool` works as expected now, etc.
This is a problem, TBH, and should be addressed. Happy to troubleshoot more if you want to let me know what you are looking for exactly.

This could be relevant: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/114#note_1524991
And this https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c2a3e929650d327c5f57ec2f646b1cb749d60843

On my side, to reproduce is easy. Just install latest version of both `gnome-keyring` and `glib2`, get into X, and try to use anything which depends on `gnome-keyring`. Result: no response from the daemon.

I'm experiencing this problem with gnome-initial-setup. It simply hangs for 30 seconds when trying to connect to gnome-keyring. Since both Debian[1][2] and Fedora[3] build gnome-keying without capabilities support, I think we should disable it too.

[1] https://salsa.debian.org/gnome-team/gnome-keyring/-/commit/4cd87240f3cc8ce077003027d10d83d289dd3554
[2] https://salsa.debian.org/gnome-team/gnome-keyring/-/commit/82a131c7095cf331dad1c2573d8f963cd9efa725
[3] https://src.fedoraproject.org/rpms/gnome-keyring/c/e4be4e4a0420d50066121a4d95e372363b78311e

I pushed gnome-keyring 1:42.1-3 to [extra-testing] with disabled capabilities support.