Bug#1114020: gnome-keyring: Need to manually ssh-add key (again?) after login
Matijs van Zuijlen
matijs at matijs.net
Fri Sep 5 12:55:42 BST 2025
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.
I should also mention that when the new gcr4 ssh agent started the first
time, I got the graphical prompt to type my ssh key passphrase and I may
have mistyped it. No new prompt appeared, however.
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.3+deb14-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-keyring depends on:
ii dbus-user-session [default-dbus-session-bus] 1.16.2-2
ii dbus-x11 [dbus-session-bus] 1.16.2-2
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-5
ii gcr 3.41.2-4
ii init-system-helpers 1.69
ii libc6 2.41-12
ii libgck-1-0 3.41.2-4
ii libgcr-base-3-1 3.41.2-4
ii libgcrypt20 1.11.2-2
ii libglib2.0-0t64 2.84.4-3
ii libsystemd0 258~rc3-1
ii p11-kit 0.25.5-3
ii pinentry-gnome3 1.3.2-3
Versions of packages gnome-keyring recommends:
ii gnome-keyring-pkcs11 48.0-3
ii libpam-gnome-keyring 48.0-3
gnome-keyring suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list