GNOME Bugzilla – Bug 617805
Crash in gnome_keyring_find_items_sync
Last modified: 2010-07-02 01:56:32 UTC
What were you doing when the application crashed? Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10706901 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome-alternative GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 257003520 vsize: 257003520 resident: 50671616 share: 25141248 rss: 50671616 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273087134 rtime: 4013 utime: 3902 stime: 111 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xa911db70 (LWP 30042)] [New Thread 0xaa920b70 (LWP 30041)] [New Thread 0xab125b70 (LWP 30040)] [New Thread 0xb0cf9b70 (LWP 30038)] [New Thread 0xb14fab70 (LWP 30037)] [New Thread 0xab926b70 (LWP 30036)] [New Thread 0xaa11fb70 (LWP 30018)] [New Thread 0xb3afbb70 (LWP 29069)] [New Thread 0xb1cfbb70 (LWP 29068)] [New Thread 0xb24fcb70 (LWP 28797)] [New Thread 0xb04f8b70 (LWP 28796)] [New Thread 0xb4856b70 (LWP 28785)] [New Thread 0xb5057b70 (LWP 28783)] 0xb77fb424 in __kernel_vsyscall ()
+ Trace 221737
Thread 1 (Thread 0xb5aa8ad0 (LWP 28776))
A debugging session is active. Inferior 1 [process 28776] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ---- Critical and fatal warnings logged during execution ---- ** evolution **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached ** evolution **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached ----------- .xsession-errors --------------------- Advertencia del gestor de ventanas: La propiedad _NET_WM_NAME en la ventana 0x340001f contiene UTF-8 inválido (gnome-panel:2033): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8 Advertencia del gestor de ventanas: La propiedad _NET_WM_ICON_NAME en la ventana 0x340001f contiene UTF-8 inválido Advertencia del gestor de ventanas: La propiedad _NET_WM_NAME en la ventana 0x340001f contiene UTF-8 inválido Advertencia del gestor de ventanas: La propiedad _NET_WM_ICON_NAME en la ventana 0x340001f contiene UTF-8 inválido Advertencia del gestor de ventanas: La propiedad _NET_WM_NAME en la ventana 0x340001f contiene UTF-8 inválido Advertencia del gestor de ventanas: La propiedad _NET_WM_ICON_NAME en la ventana 0x340001f contiene UTF-8 inválido ** (evolution:28776): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached ** (evolution:28776): CRITICAL **: file gkr-operation.c: line 350 (gkr_operation_request): should not be reached ** ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached --------------------------------------------------
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. Could you please install some debugging packages [1], start the application as normal, and reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the Details, now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] debugging packages for gnome-keyring, evolution, evolution-data-server, evolution-exchange, gtkhtml2, gtk2 and glib2 (as far as those packages are provided by your distribution). More details can be found here: http://live.gnome.org/GettingTraces
*** Bug 617961 has been marked as a duplicate of this bug. ***
*** Bug 617929 has been marked as a duplicate of this bug. ***
*** Bug 617923 has been marked as a duplicate of this bug. ***
*** Bug 618024 has been marked as a duplicate of this bug. ***
*** Bug 618259 has been marked as a duplicate of this bug. ***
*** Bug 618761 has been marked as a duplicate of this bug. ***
*** Bug 618847 has been marked as a duplicate of this bug. ***
*** Bug 619195 has been marked as a duplicate of this bug. ***
*** Bug 620475 has been marked as a duplicate of this bug. ***
I think bug should be fixed with the patch in bug 612596
*** This bug has been marked as a duplicate of bug 621913 ***