Your message dated Sat, 19 Sep 2026 16:19:44 +0100
with message-id <[email protected]>
and subject line Re: Bug#1147994: gnome-keyring 51.1-1
has caused the Debian Bug report #1147994,
regarding gnome-keyring: regression in 51.0, keyring assertion failures and
crash, asks for a password again
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147994
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 51.0-1
Dear maintainer,
the current gnome-keyring update in unstable breaks evolution.
When I start signal or evolution I'm ask for my password. This is new.
- signal works after entering the password
- evolution responds with a timeout
Going back to version 50.0-1 restores functionality. Keyring dosn't ask
for a password. I think this is a regression.
apt policy gnome-keyring gnome-keyring-pkcs11 libpam-gnome-keyring
gnome-keyring:
Installed: 50.0-1
Candidate: 50.0-1
Version table:
51.0-1 300
300 http://deb.debian.org/debian sid/main amd64 Packages
300 https://ftp.uni-mainz.de/debian sid/main amd64 Packages
*** 50.0-1 1001
500 http://deb.debian.org/debian forky/main amd64 Packages
500 https://ftp.uni-mainz.de/debian forky/main amd64 Packages
100 /var/lib/dpkg/status
gnome-keyring-pkcs11:
Installed: 50.0-1
Candidate: 50.0-1
Version table:
51.0-1 300
300 http://deb.debian.org/debian sid/main amd64 Packages
300 https://ftp.uni-mainz.de/debian sid/main amd64 Packages
*** 50.0-1 1001
500 http://deb.debian.org/debian forky/main amd64 Packages
500 https://ftp.uni-mainz.de/debian forky/main amd64 Packages
100 /var/lib/dpkg/status
libpam-gnome-keyring:
Installed: 50.0-1
Candidate: 50.0-1
Version table:
51.0-1 300
300 http://deb.debian.org/debian sid/main amd64 Packages
300 https://ftp.uni-mainz.de/debian sid/main amd64 Packages
*** 50.0-1 1001
500 http://deb.debian.org/debian forky/main amd64 Packages
500 https://ftp.uni-mainz.de/debian forky/main amd64 Packages
100 /var/lib/dpkg/status
Regards
Marc
signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Version: 51.0-2
On Sat, 19 Sep 2026 at 12:34:33 +0200, Marc wrote:
Gnome-keyring 51.1 behaves nicely and fixes the problems here.
Thanks, if the SIGSEGV is fixed for everyone, and nobody can reproduce
the SIGABRT mentioned in
https://gitlab.gnome.org/GNOME/gnome-keyring/-/work_items/197, then
let's close this.
smcv
--- End Message ---
