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 629181 - gnome-keyring-daemon crashed with SIGSEGV in g_array_append_vals()
gnome-keyring-daemon crashed with SIGSEGV in g_array_append_vals()
Status: RESOLVED FIXED
Product: gnome-keyring
Classification: Core
Component: general
2.31.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-09-09 15:03 UTC by Pedro Villavicencio
Modified: 2010-09-10 02:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32



Description Pedro Villavicencio 2010-09-09 15:03:21 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-keyring/+bug/631041

"only entered the password"

"#0  0x0097950b in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
  • #1 g_array_append_vals
    from /lib/libglib-2.0.so.0
  • #2 on_unlock_complete
    at gkd-secret-unlock.c line 168
  • #3 process_completed
    at gp11-call.c line 153
  • #4 completed_dispatch
    at gp11-call.c line 199
  • #5 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #6 ??
    from /lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #8 main
    at gkd-main.c line 846

Comment 1 Stef Walter 2010-09-10 02:52:36 UTC
I think this commit should fix the problem. Thanks for reporting this issue:

commit 5bd62371420b25e644a9fdb6dac393b273512bc5
Author: Stef Walter <stef@memberwebs.com>
Date:   Fri Sep 10 02:51:16 2010 +0000

    [dbus] Ref unlock object while performing async operation.
    
    Reference the GkdSecretUnlock object while performing an async
    operation, and unref in the callback.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=629181