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 573768 - gnome-keyring-daemon crashed with SIGSEGV in g_type_class_ref()
gnome-keyring-daemon crashed with SIGSEGV in g_type_class_ref()
Status: RESOLVED INCOMPLETE
Product: gnome-keyring
Classification: Core
Component: general
2.25.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-03-02 15:12 UTC by Sebastien Bacher
Modified: 2010-03-19 04:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26

Attachments
.xsession-errors (36.58 KB, application/octet-stream)
2009-03-03 04:36 UTC, kas 		Details
auth.log (434.29 KB, text/x-log)
2009-03-03 04:38 UTC, kas 		Details

Description Sebastien Bacher 2009-03-02 15:12:01 UTC 
This bug has been opened on http://bugs.launchpad.net/bugs/336447

"Binary package hint: gnome-keyring

after i logged in i couldnt find my ntfs partitions in the places menu so i restarted and got a message of a crash report. this is on a jaunty alpha 5 install.

gnome-keyring 2.25.91-0ubuntu1

Debug stacktrace for the crash:

+ Trace 213065

  • #0 ??
  • #1 IA__g_type_class_ref
    at /build/buildd/glib2.0-2.19.8/gobject/gtype.c line 1989
  • #2 IA__g_object_new_valist
    at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1280
  • #3 IA__g_object_new
    at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1060
  • #4 gck_user_storage_new
    at gck-user-storage.c line 971
  • #5 gck_user_module_constructor
    at gck-user-module.c line 247
  • #6 IA__g_object_newv
    at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1215
  • #7 IA__g_object_new_valist
    at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1319
  • #8 IA__g_object_new
    at /build/buildd/glib2.0-2.19.8/gobject/gobject.c line 1060
  • #9 gck_C_Initialize
    at gck-user-module.c line 86
  • #10 plex_C_Initialize
    at gck-plex-layer.c line 140
  • #11 auth_C_Initialize
    at gkr-pkcs11-auth-ep.c line 293
  • #12 gkr_pkcs11_daemon_initialize
    at gkr-pkcs11-daemon.c line 108
  • #13 gkr_daemon_complete_initialization
    at gkr-daemon.c line 629
  • #14 op_prepare_daemon_environment
    at gkr-daemon-ops.c line 1737
  • #15 client_worker_main
    at gkr-daemon-io.c line 298
  • #16 async_worker_thread
    at gkr-async.c line 269
  • #17 g_thread_create_proxy
    at /build/buildd/glib2.0-2.19.8/glib/gthread.c line 635
  • #18 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #19 clone
    from /lib/tls/i686/cmov/libc.so.6" 






Comment 1


Stef Walter





          2009-03-03 00:58:34 UTC
        



Hmm, it seems to be warning about something. Is there any output from gnome-keyring in ~/.xsession-errors? Or /var/log/auth.log? Could you attach it to this bug.






Comment 2


kas





          2009-03-03 04:36:55 UTC
        



Created attachment 129917 [details]
.xsession-errors






Comment 3


kas





          2009-03-03 04:38:17 UTC
        



Created attachment 129919 [details]
auth.log






Comment 4


Stef Walter





          2009-03-03 05:11:59 UTC
        



Hmmm, I think this has to do with bug #537555 in glib. I'll post something on the GTK mailing list. Could you check what version of glib you have installed?






Comment 5


kas





          2009-03-03 17:38:48 UTC
        



i couldn't find any package named glib, closest i found was libglib2.0-0 version: 2.19.10-0ubuntu1.  i am a total noob so i don't know. i looked at the xsession-errors and saw a lot of complaining on some custom themes i downloaded from gnome-look and deviantart. those themes were meant for older ubuntus, could that have been the cause of this crash? 






Comment 6


Stefan Sauer (gstreamer, gtkdoc dev)





          2009-03-04 07:43:38 UTC
        



In GStreamer we _ref all kind of classes before we go into multi-threaded operations, because of that (look at gstreamer/gst/gst.c::init_post()).






Comment 7


Stef Walter





          2009-03-05 03:03:16 UTC
        



Thanks Stefan. I guess these are never unrefed anywhere, right? So it would be a small (but perhaps acceptable) memory leak if gstreamer was unloaded. Do you meticulously track all the types in gstreamer add them to that list? Or have you somehow found a way to determine which ones will be problematic.

kas, can you try gnome-keyring-2.25.92 and see if this is fixed for you?






Comment 8


Stefan Sauer (gstreamer, gtkdoc dev)





          2009-03-05 09:03:18 UTC
        



yes, its a static allocation that is ever freed until the process that ses gstreamer is terminated. The memory allocated by the gtype system in anyway never released. And you are right, we are carefully watching new types in the core module and add them there. Basically we need to add all those there which might otherwise be first used from a different thread-context.







Comment 9


kas





          2009-03-05 22:06:37 UTC
        



i don't know how to reproduce the crash, it happened just twice on .91. yesterday ubuntu updated it to .92, and it hasn't crashed on me yet. i will let you know if it does.






Comment 10


Akhil Laddha





          2009-12-11 06:33:42 UTC
        



Kas, did you get similar crash any time later ?  Can you please try in 2.26.x/ 2.28.x and report back, thanks.






Comment 11


Akhil Laddha





          2010-03-19 04:06:52 UTC
        



Closing this bug report as no further information has been provided. Please 
feel free to reopen the bug if the problem still occurs with a newer
version of GNOME 2.28.2 or later, thank