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 634728 - gnome-keyring-daemon crashed with SIGSEGV in g_main_dispatch()
gnome-keyring-daemon crashed with SIGSEGV in g_main_dispatch()
Status: RESOLVED OBSOLETE
Product: gnome-keyring
Classification: Core
Component: general
2.32.x
Other Linux
: Normal critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-11-13 00:38 UTC by Cristian Aravena Romero
Modified: 2011-04-15 12:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.31/2.32

Attachments
auth.log.4 (65.08 KB, text/plain)
2010-12-06 17:23 UTC, Cristian Aravena Romero 		Details

Description Cristian Aravena Romero 2010-11-13 00:38:07 UTC 
Open bug in Launchpad.net
https://bugs.launchpad.net/bugs/674743

+ Trace 224648

  • #0 mark_as_complete
    at gkd-secret-unlock.c line 143
  • #1 on_unlock_complete
    at gkd-secret-unlock.c line 176
  • #2 process_completed
    at gp11-call.c line 153
  • #3 completed_dispatch
    at gp11-call.c line 199
  • #4 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #7 main
    at gkd-main.c line 846 






Comment 1


Fabio Durán Verdugo





          2010-11-14 02:24:30 UTC
        



if I follow this steps from launchpad report
1) Start Ubuntu
2) Open session
3) Close session
4) Reopen session
5) Open apport

I can't reproduce.

if I try to reproduce using this:

ExecutablePath: /usr/bin/gnome-keyring-daemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
ProcEnviron:
SHELL=/bin/bash
LANG=es_ES.utf8

I can't reproduce too.

Cristian exists others steps for reproduce this bug?






Comment 2


Cristian Aravena Romero





          2010-11-14 02:55:07 UTC
        



_1_ Crash, not reproducice






Comment 3


Stef Walter





          2010-12-06 12:23:04 UTC
        



Is there any output in /var/log/auth.log from gnome-keyring-daemon around the time this crash occurs?






Comment 4


Cristian Aravena Romero





          2010-12-06 17:23:46 UTC
        



Created attachment 175941 [details]
auth.log.4

~Nov 12 20:17:XX






Comment 5


Stef Walter





          2011-01-19 22:50:37 UTC
        



I found this in that log file around the date of the crash. 

Nov 12 20:18:02 VGN-NS130FE gnome-keyring-daemon[1717]: GLib-GObject: invalid unclassed pointer in cast to `GkdSecretUnlock'

Sadly, in order to fix this we need a better stack trace. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!






Comment 6


Akhil Laddha





          2011-03-03 11:16:18 UTC
        



@Cristian, were you able to collect traces with debug symbols ?






Comment 7


Cristian Aravena Romero





          2011-03-03 17:52:13 UTC
        



@Akhil, now not crash. My system update