Bug#1148156: Bug#1147994: gnome-keyring: regression in 51.0, keyring assertion failures and crash, asks for a password again

[Simon McVittie]

Control: forcemerge 1147994 1148156
Control: forwarded 1147994 https://gitlab.gnome.org/GNOME/gnome-keyring/-/work_items/197
Control: retitle 1147994 gnome-keyring: regression in 51.0, keyring assertion failures and crash, asks for a password again
Control: severity 1147994 important
Control: tags 1147994 + moreinfo
Control: affects 1147994 + evolution seahorse

On Tue, 15 Sep 2026 at 22:15:38 +0200, Marc wrote:
>the current gnome-keyring update in unstable breaks evolution

On Tue, 15 Sep 2026 at 22:53:36 +0200, Christoph Anton Mitterer wrote:
>Sep 15 22:04:00 heisenberg kernel: gnome-keyring-d[689747]: segfault at f00dface ip 00007f2fc08b5482 sp 00007fffdb017550 error 4 in libgck-1.so.0.0.0[1d482,7f2fc08a2000+1d000] likely on CPU 9 (core 17, socket 0)

This is likely to be fixed in 51.0-2: I was seeing a similar crash and 
it's resolved by the updated version. The updated version has been 
confirmed to fix #1147940 which had very similar symptoms.

On the upstream issue there is an unconfirmed report of different 
assertion failures causing a different crash (SIGABRT, not SIGSEGV), so 
I'm leaving this open with a reduced severity instead of closing it 
immediately. If someone can reproduce that different crash, we'll need a 
backtrace or more detailed steps to reproduce.

     smcv