GNOME Bugzilla – Bug 421410
gnome-keyring-daemon crashed with SIGSEGV in strcmp()
Last modified: 2009-03-03 03:59:27 UTC
The bug has been opened on https://launchpad.net/bugs/94612 "Binary package hint: gnome-keyring I was remove a key... ProblemType: Crash Architecture: i386 Date: Wed Mar 21 21:50:32 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-keyring-daemon Package: gnome-keyring 0.8.0-0ubuntu1 PackageArchitecture: i386 ProcCmdline: /usr/bin/gnome-keyring-daemon ... .
+ Trace 121073
Thread 1 (process 5267)
Corresponding code line: " if (strcmp (keyring->keyring_name, name) == 0) {" gdb on the crash: (gdb) p *keyring $1 = {file = 0x6d6f682f <Address 0x6d6f682f out of bounds>, file_mtime = 1969958757, password = 0x696d7572 <Address 0x696d7572 out of bounds>, locked = 1731080046, asking_password = 1701670766, salt = "2/keyrin", hash_iterations = 29543, keyring_name = 0x0, items = 0x19, ctime = 134627384, mtime = 134635088, lock_on_idle = 1768781170, lock_timeout = 12142}
*** Bug 404551 has been marked as a duplicate of this bug. ***
Easy to reproduce, create and desktroy keyrings result in this Valgrind report: ==5106== Invalid read of size 4 ==5106== at 0x8050B92: find_keyring (gnome-keyring-daemon.c:670) ==5106== by 0x805420B: update_default (gnome-keyring-daemon-file.c:874) ==5106== by 0x80552E8: update_keyrings_from_disk (gnome-keyring-daemon-file.c:958) ==5106== by 0x80560E8: gnome_keyring_client_state_machine (gnome-keyring-daemon-io.c:451) ==5106== by 0x80564AD: gnome_keyring_client_io (gnome-keyring-daemon-io.c:368) ==5106== by 0x407BC0C: g_io_unix_dispatch (giounix.c:162) ==5106== by 0x4052651: g_main_context_dispatch (gmain.c:2045) ==5106== by 0x405562E: g_main_context_iterate (gmain.c:2677) ==5106== by 0x40559D8: g_main_loop_run (gmain.c:2881) ==5106== by 0x8053A4E: main (gnome-keyring-daemon.c:3003) ==5106== Address 0x426C7D8 is 32 bytes inside a block of size 56 free'd ==5106== at 0x402123A: free (vg_replace_malloc.c:233) ==5106== by 0x4059990: g_free (gmem.c:187) ==5106== by 0x8053048: op_delete_keyring_execute (gnome-keyring-daemon.c:1146) ==5106== by 0x805630D: gnome_keyring_client_state_machine (gnome-keyring-daemon-io.c:498) ==5106== by 0x80564AD: gnome_keyring_client_io (gnome-keyring-daemon-io.c:368) ==5106== by 0x407BC0C: g_io_unix_dispatch (giounix.c:162) ==5106== by 0x4052651: g_main_context_dispatch (gmain.c:2045) ==5106== by 0x405562E: g_main_context_iterate (gmain.c:2677) ==5106== by 0x40559D8: g_main_loop_run (gmain.c:2881) ==5106== by 0x8053A4E: main (gnome-keyring-daemon.c:3003)
And this is gnome-keyring-manager bug
Are you sure? The crash is in gnome-keyring-daemon. Can you duplicate this with 2.19.4?
gnome-keyring-manager has been deprecated and superseded by Seahorse more than one year ago. There has not been any active code development for more than a year. This bug will probably soon be closed as WONTFIX or OBSOLETE.
Thanks for taking the time to report this bug. However, gnome-keyring-manager won't be developed anymore and it has been superseded by Seahorse.
re-assigning to gnome-keyring, since the bug was an issue with the daemon not with the manager. thanks.
I believe this has been fixed in recent versions of gnome-keyring. Tons of crashers have been fixed. In addition the above valgrind errors are no longer produced by creating or deleting keyrings.