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 603789 - gnome-keyring-daemon crashed with SIGSEGV
gnome-keyring-daemon crashed with SIGSEGV
Status: RESOLVED INCOMPLETE
Product: gnome-keyring
Classification: Core
Component: general
2.28.x
Other Linux
: High critical
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-12-04 14:29 UTC by Pedro Villavicencio
Modified: 2010-02-09 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-12-04 14:29:15 UTC
this report has been filed here:

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

"trying to add google calendar, gnome key ring crashed"

".

Thread 3 (process 2188)

  • #0 __kernel_vsyscall
  • #1 do_sigwait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 sigwait
    from /lib/tls/i686/cmov/libpthread.so.0
  • #3 signal_thread
    at gkr-daemon.c line 347
  • #4 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 130

Comment 1 Stef Walter 2010-02-07 19:01:37 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. 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 2 Pedro Villavicencio 2010-02-09 14:21:43 UTC
Hello Stef, may you please tell me which symbol is missing so i can go ahead and ask the reporters for a better one? https://bugzilla.gnome.org/page.cgi?id=trace.html&trace_id=219451 shows that the trace is complete but the trace parser it's only showing a part of it here at the bugzilla summary page. Thanks in advance.