GNOME Bugzilla – Bug 521835
crash in Tasks:
Last modified: 2008-03-12 16:31:13 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.14-64.fc7 #1 SMP Sun Jan 20 23:54:08 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 131219456 vsize: 131219456 resident: 51585024 share: 35483648 rss: 51585024 rss_rlim: 4294967295 CPU usage: start_time: 1205260318 rtime: 683 utime: 635 stime: 48 cutime:43 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 -1208883488 (LWP 3658)] [New Thread -1302746224 (LWP 3672)] [New Thread -1217737840 (LWP 3670)] [New Thread -1229980784 (LWP 3663)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 192108
Thread 1 (Thread -1208883488 (LWP 3658))
----------- .xsession-errors (39 sec old) --------------------- index:0 index:0 index:0 index:0 index:0 Autoselected keyboard map en-us Autoselected keyboard map en-us CalDAV Eplugin starting up ... ** (evolution:3658): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:3658): DEBUG: mailto URL program: evolution (evolution:3658): e-data-server-DEBUG: Loading categories from "/home/itis/.evolution/categories.xml" (evolution:3658): e-data-server-DEBUG: Loaded 29 categories Autoselected keyboard map en-us ERROR: recv: Connection reset by peer CalDAV Eplugin starting up ... --------------------------------------------------
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 501900 ***