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 612435 - gnome-keyring-daemon crashed with SIGSEGV in g_list_prepend()
gnome-keyring-daemon crashed with SIGSEGV in g_list_prepend()
Status: RESOLVED INCOMPLETE
Product: gnome-keyring
Classification: Core
Component: general
2.29.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-03-10 14:34 UTC by Sebastien Bacher
Modified: 2011-01-27 03:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2010-03-10 14:34:26 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/528268

"gnome-keyring-daemon crashes while trying to add accounts in empathy

gnome-keyring 2.29.90git20100218-0ubuntu2

+ Trace 220907

  • #0 g_list_prepend
    from /lib/libglib-2.0.so.0
  • #1 _gck_manager_register_object
    at gck-manager.c line 435
  • #2 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #3 ??
    from /usr/lib/libgobject-2.0.so.0
  • #4 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #5 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #6 add_transient_object
    at gck-module.c line 460
  • #7 gck_session_complete_object_creation
    at gck-session.c line 878
  • #8 factory_create_credential
    at gck-credential.c line 96
  • #9 gck_session_create_object_for_factory
    at gck-session.c line 793
  • #10 gck_aes_mechanism_unwrap
    at gck-aes-mechanism.c line 224
  • #11 gck_session_C_UnwrapKey
    at gck-session.c line 1577
  • #12 gck_C_UnwrapKey
    at ../../pkcs11/gck/gck-module-ep.h line 1382
  • #13 plex_C_UnwrapKey
    at gck-plex-layer.c line 819
  • #14 perform_unwrap_key
    at gp11-session.c line 1654
  • #15 _gp11_call_sync
    at gp11-call.c line 400
  • #16 gp11_session_unwrap_key_full
    at gp11-session.c line 1749
  • #17 gkd_secret_session_create_credential
    at gkd-secret-session.c line 711
  • #18 gkd_secret_create_with_secret
    at gkd-secret-create.c line 294
  • #19 gkd_secret_create_prompt_ready
    at gkd-secret-create.c line 100
  • #20 gkd_secret_prompt_responded
    at gkd-secret-prompt.c line 234
  • #21 gkd_prompt_marshal_BOOLEAN__VOID
    at gkd-prompt-marshal.c line 82
  • #22 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #23 ??
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #25 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #26 on_io_completed
    at gkd-prompt.c line 129
  • #27 cb_source_dispatch
    at egg-spawn.c line 142
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 ??
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 main
    at gkd-main.c line 795 


The version used is a git snapshot which has been made on 2010-02-18
Comment 1 Stef Walter 2010-12-13 10:07:38 UTC 
How often does this occur? Do we know if it was just a random occurrence or whether a certain action preceded the crash?
Comment 2 Akhil Laddha 2011-01-27 03:58:10 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!