GNOME Bugzilla – Bug 404551
gnome-keyring-daemon crashed with SIGSEGV in strcmp()
Last modified: 2007-06-22 13:11:28 UTC
That bug has been opened on https://launchpad.net/ubuntu/+source/gnome-keyring/+bug/83326 "Binary package hint: gnome-keyring I simply entered my Wireless LAN WPA key with NetworkManager, then I had the keyring window asking for a password to create a new keyring. I created one and 10s after it crashed. ... Package: gnome-keyring 0.7.3-0ubuntu1 ..." Debug backtrace for the crash: (gdb) bt full
+ Trace 108132
The corresponding line: " if (strcmp (keyring->keyring_name, name) == 0) {" (gdb) p *keyring $3 = {file = 0x0, file_mtime = 1953705829, password = 0x62617267 <Address 0x62617267 out of bounds>, locked = 774861413, asking_password = 1836019303, salt = "e2/keyri", hash_iterations = 7563118, keyring_name = 0x7469726f <Address 0x7469726f out of bounds>, items = 0x79, ctime = 48, mtime = 17, lock_on_idle = 0, lock_timeout = 3697781}
Bummer. Looks like we've freed a GnomeKeyring object still in the list :( This bug is going to be challenging to find without being able to duplicate it. All the keyring allocation and deallocation in update_keyrings_from_disk() is definitely suspect.
*** This bug has been marked as a duplicate of 421410 ***
Either #421410 and this one are not the same, or #421410 is not about gnome-keyring-manager. Stef? Also in current ubuntu gutsy it's pretty easy to duplicate; actually anything that uses libgnome-keyring.so keeps crashing.
They look like the same bug. What version of gnome-keyring does gutsy ship?
Actually if libgnome-keyring.so is the thing that crashes, then you've found a bug that is altogether unrelated to this. Could you file it and/or provide a stack trace?