Package: gnome-keyring Version: 42.1-1+b2 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear Maintainer, About two months ago I upgraded this desktop from Bullseye to Bookworm. With Bullseye, and Buster prior, gnome-keyring-daemon worked reliably and without issue for automatically handling SSH keys and other credentials. After the upgrade it wasn't too long before I was puzzled as to why I was being prompted for SSH key passwords. A short investigation revealed the daemon was not running. I rebooted the system and the daemon was running and handling SSH key passwords as I expected and I regarded the matter as an upgrade glitch until some time later the prompts for SSH keys passwords returned. Puzzled, I posted a message to the Debian User mailing list: https://lists.debian.org/debian-user/2023/08/msg00406.html Which did receive one followup. Two weeks later I posted to the GNOME Keyring discourse: https://discourse.gnome.org/t/keyring-crashing-troubleshooting-help-please/16880 and was advised to open issues in the GNOME Keyring repository that I have done: https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/135 https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/136 Issue #135 has been updated with requested GDB output. Since that time it doesn't matter if I logout/login or worm/cold restart the system, gnome-keying-daemon will reliably shut down after about an hour, restart but be useless having lost login credentials and then shut down permanently until the next login event. At one point I even moved the files under ~/.local/share/keyrings to a temporary directory and let the daemon create new ones only for the early shut downs to continue. I also found that Chromium directly accesses login.keyring under that directory so I restored the original to give access to stored passwords under Chromium (as an aside, when the daemon is not running and I start Chromium, I will get the GTK PIN Entry dialog which opens the keyring for Chromium and it stays open until Chromium is closed). None of these actions have had any effect on keeping the daemon running. Also, I have noticed no such issues on my laptop also running Debian 12 and the GNOME desktop. One difference between the two systems is that I have Chromium installed through Flatpack on the laptop rather than use the provided Debian package (historical reasons). On this desktop the Debian Chromium package is installed. Also, this desktop has snapd installed to run the latest version of Hugo. This was installed under Bullseye with no apparent side effects. Mostly I am recording this to provide information of the issues in GNOME's Gitlab for the benefit of any future resolution. - -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bookworm-fasttrack') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set 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.14.10-1~deb12u1 ii dbus-x11 [dbus-session-bus] 1.14.10-1~deb12u1 ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4 ii gcr 3.41.1-1+b1 ii init-system-helpers 1.65.2 ii libc6 2.36-9+deb12u3 ii libgck-1-0 3.41.1-1+b1 ii libgcr-base-3-1 3.41.1-1+b1 ii libgcrypt20 1.10.1-3 ii libglib2.0-0 2.74.6-2 ii libsystemd0 252.17-1~deb12u1 ii p11-kit 0.24.1-2 ii pinentry-gnome3 1.2.1-1 Versions of packages gnome-keyring recommends: ii gnome-keyring-pkcs11 42.1-1+b2 ii libpam-gnome-keyring 42.1-1+b2 gnome-keyring suggests no packages. - -- debconf-show failed -----BEGIN PGP SIGNATURE----- iGsEARECACsWIQSC1k9rDmfNQfaJu6b7LFEw1VqIGQUCZSqDpg0cbjBuYkBuMG5i LnVzAAoJEPssUTDVWogZ3HMAnj+rZguubzEymOl0Rzh8vWAUCZ2iAJ4iyU4fKTQp nMDTtoAiXBI4SQLB/Q== =5JZA -----END PGP SIGNATURE-----
