Package: gnome-keyring Version: 3.36.0-1 Severity: normal Dear Maintainer,
When connection through ssh from system A to system B the gnome-keyring-daemon "eat" 100% CPU and the connection is impossible. Killing the daemon is the only solution to have a working connection. But if you didn't notice the fact that a process is eating 100% CPU you can't connect to another system without a reboot. Remark : The first connection since reboot is OK, the next hits that bug. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=C 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.12.20-1 ii dbus-x11 [dbus-session-bus] 1.12.20-1 ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1 ii gcr 3.38.1-1 ii libc6 2.31-9 ii libcap-ng0 0.7.9-2.2+b1 ii libcap2-bin 1:2.44-1 ii libgck-1-0 3.38.1-1 ii libgcr-base-3-1 3.38.1-1 ii libgcrypt20 1.8.7-2 ii libglib2.0-0 2.66.4-1 ii p11-kit 0.23.22-1 ii pinentry-gnome3 1.1.0-4 Versions of packages gnome-keyring recommends: ii gnome-keyring-pkcs11 3.36.0-1 ii libpam-gnome-keyring 3.36.0-1 gnome-keyring suggests no packages. -- no debconf information