GNOME Bugzilla – Bug 546688
searching for a key
Last modified: 2008-09-07 15:17:30 UTC
Searching for a key. This always happens if I enter text that is not a key ID, or a key ID starting with 0x. ** (seahorse:12958): CRITICAL **: update_uids: assertion `SEAHORSE_IS_PGP_SOURCE (source)' failed ** (seahorse:12958): CRITICAL **: calc_validity: assertion `pkey->uids' failed ** (seahorse:12958): CRITICAL **: update_uids: assertion `SEAHORSE_IS_PGP_SOURCE (source)' failed ** (seahorse:12958): CRITICAL **: calc_validity: assertion `pkey->uids' failed (seahorse:12958): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb7055940 (LWP 12958)] 0xb7151c37 in strstr () from /lib/tls/i686/cmov/libc.so.6 (gdb) thread apply all bt
+ Trace 204751
Thread 1 (Thread 0xb7055940 (LWP 12958))
Just happened with 2.23.91 again. See https://bugs.edge.launchpad.net/ubuntu/+source/seahorse/+bug/258149 Backtrace: (gdb) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/bin/seahorse [Thread debugging using libthread_db enabled] [New Thread 0xb6f4ab40 (LWP 14500)] ** Message: init gpgme version 1.1.6 [New Thread 0xb65d5b90 (LWP 14512)] (seahorse:14500): Gtk-WARNING **: Inserting action group 'key' into UI manager which already has a group with this name ** (seahorse:14500): CRITICAL **: update_uids: assertion `SEAHORSE_IS_PGP_SOURCE (source)' failed ** (seahorse:14500): CRITICAL **: calc_validity: assertion `pkey->uids' failed ** (seahorse:14500): CRITICAL **: update_uids: assertion `SEAHORSE_IS_PGP_SOURCE (source)' failed ** (seahorse:14500): CRITICAL **: calc_validity: assertion `pkey->uids' failed (seahorse:14500): GLib-CRITICAL **: g_utf8_casefold: assertion `str != NULL' failed [New Thread 0xb5bffb90 (LWP 14513)] [New Thread 0xb53feb90 (LWP 14514)] [Thread 0xb53feb90 (LWP 14514) exited] [Thread 0xb5bffb90 (LWP 14513) exited] [Thread 0xb65d5b90 (LWP 14512) exited] Program received signal SIGSEGV, Segmentation fault.
+ Trace 206322
Thread 3069487936 (LWP 14500)
Thread 1 (Thread 0xb6f4ab40 (LWP 14500))
The program is running. Exit anyway? (y or n)
This should be fixed with this commit: 2008-09-07 Stef Walter <stef@memberwebs.com> * libseahorse/seahorse-key.c: Fill in abstract methods properly on the SeahorseObject class. Fixes crash.