seahorse crashed with SIGSEGV in strlen()

[Tiago Sousa]

Binary package hint: seahorse

It happens when I try to access to the passwords tab

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Jun 27 17:03:21 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/seahorse
NonfreeKernelModules: fglrx
Package: seahorse 2.19.4-0ubuntu1
PackageArchitecture: i386
ProcCmdline: seahorse
ProcCwd: /home/tiagoboldt
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: seahorse
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 gnome_keyring_memory_strdup ()
 gnome_keyring_item_info_copy ()
 ?? ()
 ?? ()
Title: seahorse crashed with SIGSEGV in strlen()
Uname: Linux Niath 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

[Stéphane Loeuillet (leroutier)]

I believe it is related to the bug that was just fixed in network manager 0.6.5 with encrypted wifi

Looks like a NULL check is missing (default keyring is NULL now)

https://bugs.launchpad.net/ubuntu/+bug/121228/

[Sebastien Bacher (seb128)]

Thanks for your bug report. Please try to obtain a debug backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Stéphane Loeuillet (leroutier)]

I'll try to do it tonight on my x86-64 box (as for now I'm at work on crappy FC6)
Is there a way to make apport add information to an existing bug report rather than creating a new one ?

[Stéphane Loeuillet (leroutier)]

Starting program: /usr/bin/seahorse
[Thread debugging using libthread_db enabled]
[New Thread 47341985012128 (LWP 15111)]
** Message: init gpgme version 1.1.2

***MEMORY-WARNING***: [15111]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this program is likely to crash, leak or unexpectedly abort soon...

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47341985012128 (LWP 15111)]
0x00002b0ea73e0b70 in strlen () from /lib/libc.so.6
(gdb) bt
#0 0x00002b0ea73e0b70 in strlen () from /lib/libc.so.6
#1 0x00002b0ea2cde976 in gnome_keyring_memory_strdup (str=0x0) at gnome-keyring-memory.c:252
#2 0x00002b0ea2cde654 in gnome_keyring_item_info_copy (item_info=0x707790) at gnome-keyring-utils.c:182
#3 0x000000000042f73b in item_info_ready (result=<value optimized out>, info=0xc01c43, lop=0xc3d940) at seahorse-gkeyring-source.c:170
#4 0x00002b0ea2cda142 in gnome_keyring_get_item_info_reply (op=0xc39ac0) at gnome-keyring.c:1882
#5 0x00002b0ea2cd92a5 in operation_io (io_channel=<value optimized out>, cond=G_IO_IN, callback_data=<value optimized out>) at gnome-keyring.c:538
#6 0x00002b0ea6eb4fd3 in IA__g_main_context_dispatch (context=0x6d5820) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2061
#7 0x00002b0ea6eb82dd in g_main_context_iterate (context=0x6d5820, block=1, dispatch=1, self=<value optimized out>) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2694
#8 0x00002b0ea6eb85ea in IA__g_main_loop_run (loop=0xa40f30) at /build/buildd/glib2.0-2.13.5/glib/gmain.c:2898
#9 0x00002b0ea386f743 in IA__gtk_main () at /build/buildd/gtk+2.0-2.11.4/gtk/gtkmain.c:1144
#10 0x000000000041d9de in main (argc=1, argv=0x7fff0b5ffcd8) at main.c:88

[Stéphane Loeuillet (leroutier)]

What looks like a related bug, it crashed network-manager applet and a work-around was added to it :
https://bugs.launchpad.net/gnome-keyring/+bug/83326
https://bugs.launchpad.net/gnome-keyring/+bug/121228

But the real bug was/is in gnome-keyring lib :
http://bugzilla.gnome.org/show_bug.cgi?id=451710

So, the real culprit is libgnome-keyring
All apps using it keep crashing unless they're patched like network-manager applet was

[Mario Vukelic (kreuzsakra)]

I have seen this crash too and wanted to note that one effect seems to be that seahorse does not display my keys (own private/public pair, keys of people I added to the keyring) anymore. It seems that it does display keys it automatically added since the issue appeared.
I also can't encrypt in Evolution anymore.

[Greg Grossmeier (greg.grossmeier)]

If the upstream bug report is correct, this bug has been fixed.

If anyone is still experiencing this issue, please feel free to reopen the bug.