GNOME Bugzilla – Bug 473676
crash in Tasks:
Last modified: 2007-09-24 17:54:54 UTC
Version: 2.10 What were you doing when the application crashed? 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.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 140361728 vsize: 140361728 resident: 40902656 share: 32604160 rss: 40902656 rss_rlim: 4294967295 CPU usage: start_time: 1188934223 rtime: 128 utime: 100 stime: 28 cutime:2 cstime: 4 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208842528 (LWP 3958)] [New Thread -1269834864 (LWP 4184)] [New Thread -1259345008 (LWP 4111)] [New Thread -1248855152 (LWP 4067)] [New Thread -1221432432 (LWP 4066)] [New Thread -1210942576 (LWP 4064)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 160472
Thread 1 (Thread -1208842528 (LWP 3958))
----------- .xsession-errors (16 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:3958): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3958): DEBUG: mailto URL program: evolution 20070718T133000 is a recurrence instance 040000008200E00074C5B7101A82E00800000000A0F599BC9956C701000000000000000010000000287E5C5B540DE443B241BC5BCBBDB045 has recurrences 20070718T133000 is a recurrence instance 20070808T150350Z-4050-500-1-0@mxlrmt-190.corp.mxlogic.com has recurrences --------------------------------------------------
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 364700 ***