GNOME Bugzilla – Bug 533743
crash in Evolution Mail and Calendar: Changing folder subscrip...
Last modified: 2009-11-23 16:13:09 UTC
What were you doing when the application crashed? Changing folder subscription for account Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Gion Memory status: size: 112455680 vsize: 112455680 resident: 43958272 share: 22482944 rss: 43958272 rss_rlim: 4294967295 CPU usage: start_time: 1211138237 rtime: 2112 utime: 1980 stime: 132 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6812740 (LWP 1842)] [New Thread 0xb1940b90 (LWP 2180)] [New Thread 0xb39ffb90 (LWP 2054)] [New Thread 0xb4627b90 (LWP 2053)] [New Thread 0xb5629b90 (LWP 1851)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198043
Thread 1 (Thread 0xb6812740 (LWP 1842))
----------- .xsession-errors (93160 sec old) --------------------- ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045628,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045629,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 2 is not equal to the current group from the event: 0 ![1211045629,000,xklavier_evt_xkb.c:xkl_xkb_process_x_ev ...Too much output, ignoring rest... --------------------------------------------------
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!
Created attachment 111433 [details] evolution crash trace I'm changing folder subscriptions, actually uncheck and then check again initially checked folder.
thanks, looks good.
+ Trace 198914
Hmm, Thread 2 has also something useful. One of these caused that. It's scary to see a call like this: g_async_queue_unlock (queue=0x0); there shouldn't be used NULL for sure. but that seems to be a thing deep in glib, not much to do with evo on a first look (of course, evo could pass there some garbage, I know).
+ Trace 207120
Thread 2 (Thread 0xb2cbcb90 (LWP 11103))
*** Bug 558624 has been marked as a duplicate of this bug. ***
*** Bug 565408 has been marked as a duplicate of this bug. ***
Seems very similar to bug #558337, and I'm quite sure the fix from there fixes this one too.
*** Bug 571957 has been marked as a duplicate of this bug. ***
*** Bug 575350 has been marked as a duplicate of this bug. ***
I'm closing this per comment #7. *** This bug has been marked as a duplicate of bug 558337 ***