Bug#1114020: gnome-keyring: Need to manually ssh-add key (again?) after login

[Alessandro Astone]

On 05/09/2025 13:55, Matijs van Zuijlen wrote:
> Package: gnome-keyring
> Version: 48.0-3
> Severity: normal
> 
> Since the switch to gcr4, I have the following problem:
> 
> When I log in to GNOME, if I run `ssh some.host`, it hangs. `ssh-add -l`
> shows my key, and identifies it as `matijs at bean`:
> 
>      $ ssh-add -l                                                                                                                                                                           *~
>      2048 SHA256:yadayadayada matijs at bean (RSA)
> 
> If I then run ssh-add and type my passphrase, `ssh-add -l` reports the
> same key but identified by the file name:
> 
>      $ ssh-add -l                                                                                                                                                                           *~
>      2048 SHA256:yadayadayada /home/matijs/.ssh/id_rsa (RSA)
> 
> After this, `ssh some.host` works. It seems the earlier failed attemts
> also leave `ssh-add` processes hanging around, taking up some CPU.

Your conclusion makes sense to me, given the available information.

Indeed the ssh agent daemon spawns an ssh-add process and synchronously 
waits for the process to end. If ssh-add never terminates, it probably 
renders the agent unresponsive making ssh requests hang.

But I cannot reproduce the issue (on Ubuntu 25.10 with the same 
gnome-keyring/gcr4 ssh-agent changes).