After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 404551 - gnome-keyring-daemon crashed with SIGSEGV in strcmp()
gnome-keyring-daemon crashed with SIGSEGV in strcmp()
Status: RESOLVED DUPLICATE of bug 421410
Product: gnome-keyring
Classification: Core
Component: general
0.7.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-02-05 11:06 UTC by Sebastien Bacher
Modified: 2007-06-22 13:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Sebastien Bacher 2007-02-05 11:06:24 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
  • #0 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #1 find_keyring
    at gnome-keyring-daemon.c line 666
  • #2 update_keyrings_from_disk
    at gnome-keyring-daemon-file.c line 940
  • #3 gnome_keyring_client_state_machine
    at gnome-keyring-daemon-io.c line 492
  • #4 gnome_keyring_ask_iterate
    at gnome-keyring-daemon.c line 2728
  • #5 ask_io
    at gnome-keyring-daemon.c line 2491
  • #6 g_io_unix_dispatch
    at giounix.c line 162
  • #7 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #8 g_main_context_iterate
    at gmain.c line 2677
  • #9 IA__g_main_loop_run
    at gmain.c line 2881

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}
Comment 1 Stef Walter 2007-02-12 17:44:10 UTC
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. 
Comment 2 Stef Walter 2007-04-07 14:38:09 UTC

*** This bug has been marked as a duplicate of 421410 ***
Comment 3 Enver ALTIN 2007-06-22 11:18:02 UTC
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.
Comment 4 Stef Walter 2007-06-22 12:59:03 UTC
They look like the same bug. 

What version of gnome-keyring does gutsy ship?
Comment 5 Stef Walter 2007-06-22 13:11:28 UTC
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?