GNOME Bugzilla – Bug 490137
crash in Tasks: Viewing a message with a...
Last modified: 2008-04-04 14:11:07 UTC
Version: 2.10 What were you doing when the application crashed? Viewing a message with a forwarded meeting notice Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.7-85.fc7 #1 SMP Fri Sep 21 19:53:05 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve-Tangerine Icon Theme: Crux Memory status: size: 159801344 vsize: 159801344 resident: 64049152 share: 41222144 rss: 64049152 rss_rlim: 4294967295 CPU usage: start_time: 1193318299 rtime: 814 utime: 761 stime: 53 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208613152 (LWP 26868)] [New Thread -1264596080 (LWP 27002)] [New Thread -1308734576 (LWP 26921)] [New Thread -1233126512 (LWP 26881)] 0x00110402 in __kernel_vsyscall ()
+ Trace 172767
Thread 1 (Thread -1208613152 (LWP 26868))
----------- .xsession-errors (6 sec old) --------------------- Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Increasing itip formatter search count to 3 Increasing itip formatter search count to 4 Decreasing itip formatter search count to 3 Decreasing itip formatter search count to 2 Decreasing itip formatter search count to 1 Decreasing itip formatter search count to 0 calendar selection changed Increasing itip formatter search count to 1 Increasing itip formatter search count to 2 Increasing itip formatter search count to 3 Increasing itip formatter search count to 4 Decreasing itip formatter search count to 2 (evolution:26868): libecal-WARNING **: e-cal.c:2789: Unable to contact backend --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 468427 ***