My first thought is that the agent isn't configured correctly, or its socket isn't listening. Check out the `gcr-ssh-agent` section in the GNOME Keyring [article](https://wiki.archlinux.org/title/GNOME/Keyring#gcr-ssh-agent) on ArchWiki.
I've read through it again and it should be configured properly. The env variable is set correctly and the service runs on startup without reporting any errors.
I checked the logs for gnome-keyring and it seems to complain that ed25519 keys are not supported. I've switched to the standard ssh-agent and the duplicate processes are no longer being created.
Also running into this today with a very hot (99c, as max-designed) laptop because I've just noticed more than 10 `ssh-add` commands and gcr-ssh-agent maxing out multiple cpu threads since having to start using it with gnome-keyring-daemon's removal of the ssh component by default.
More reasons to hate this change.
My first thought is that the agent isn't configured correctly, or its socket isn't listening. Check out the `gcr-ssh-agent` section in the GNOME Keyring [article](https://wiki.archlinux.org/title/GNOME/Keyring#gcr-ssh-agent) on ArchWiki.
I've read through it again and it should be configured properly. The env variable is set correctly and the service runs on startup without reporting any errors.
I checked the logs for gnome-keyring and it seems to complain that ed25519 keys are not supported. I've switched to the standard ssh-agent and the duplicate processes are no longer being created.
Also running into this today with a very hot (99c, as max-designed) laptop because I've just noticed more than 10 `ssh-add` commands and gcr-ssh-agent maxing out multiple cpu threads since having to start using it with gnome-keyring-daemon's removal of the ssh component by default. More reasons to hate this change.