GNOME Bugzilla – Bug 580319
crash in Evolution Mail and Calendar: I wasn't actively doing ...
Last modified: 2009-04-26 20:01:52 UTC
What were you doing when the application crashed? I wasn't actively doing anything with the application. Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.21-170.2.35.vanilla.fc10.x86_64 #1 SMP Tue Mar 31 06:57:56 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 1035096064 vsize: 1035096064 resident: 194428928 share: 24346624 rss: 194428928 rss_rlim: 18446744073709551615 CPU usage: start_time: 1240701624 rtime: 9539 utime: 7597 stime: 1942 cutime:3 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fa3822ef7f0 (LWP 20339)] [New Thread 0x7fa358de2950 (LWP 27850)] [New Thread 0x7fa3512c8950 (LWP 27849)] [New Thread 0x7fa362c34950 (LWP 21561)] [New Thread 0x7fa3583eb950 (LWP 21048)] [New Thread 0x7fa358bec950 (LWP 21009)] [New Thread 0x7fa363c36950 (LWP 20946)] [New Thread 0x7fa360b6f950 (LWP 20836)] [New Thread 0x7fa361370950 (LWP 20691)] [New Thread 0x7fa362228950 (LWP 20681)] [New Thread 0x7fa363435950 (LWP 20664)] [New Thread 0x7fa36465f950 (LWP 20661)] [New Thread 0x7fa364e60950 (LWP 20660)] 0x00007fa37e397c2f in __libc_waitpid (pid=24508, stat_loc=0x7fff8a37b660, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 214819
Thread 1 (Thread 0x7fa3822ef7f0 (LWP 20339))
----------- .xsession-errors (40 sec old) --------------------- (imsettings-applet:6397): libimsettings-xim-CRITICAL **: sequence_lookup: assertion `seq->candidates != NULL' failed [BUG][ 1240770104.636306] xim_proxy_client_protocol_real_xim_forward_event: The pending key event counter is overflowed (imsettings-applet:6397): libimsettings-xim-CRITICAL **: sequence_lookup: assertion `seq->candidates != NULL' failed [BUG][ 1240770104.870467] xim_proxy_client_protocol_real_xim_forward_event: The pending key event counter is overflowed (imsettings-applet:6397): libimsettings-xim-CRITICAL **: sequence_lookup: assertion `seq->candidates != NULL' failed [BUG][ 1240770105.746319] xim_proxy_client_protocol_real_xim_forward_event: The pending key event counter is overflowed (imsettings-applet:6397): libimsettings-xim-CRITICAL **: sequence_lookup: assertion `seq->candidates != NULL' failed [BUG][ 1240770105.985510] xim_proxy_client_protocol_real_xim_forward_event: The pending key event counter is overflowed (imsettings-applet:6397): libimsettings-xim-CRITICAL **: sequence_lookup: assertion `seq->candidates != NULL' failed [BUG][ 1240770106.161599] xim_proxy_client_protocol_real_xim_forward_event: The pending key event counter is overflowed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 563866 ***