GNOME Bugzilla – Bug 519048
crash in Tasks:
Last modified: 2008-02-27 14:40:16 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.1-41.fc7 #1 SMP Fri Jul 27 18:10:34 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: humility-icons-MERGE Memory status: size: 120123392 vsize: 120123392 resident: 40206336 share: 32956416 rss: 40206336 rss_rlim: 4294967295 CPU usage: start_time: 1204119438 rtime: 405 utime: 366 stime: 39 cutime:2 cstime: 6 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 -1208981792 (LWP 13869)] [New Thread -1297106032 (LWP 14557)] [New Thread -1255146608 (LWP 13921)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 190617
Thread 1 (Thread -1208981792 (LWP 13869))
----------- .xsession-errors (22 sec old) --------------------- ** (<unknown>:4206): WARNING **: Failed to send buffer ** (<unknown>:4206): WARNING **: Failed to send buffer GTK Accessibility Module initialized Bonobo accessibility support initialized CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:13869): DEBUG: mailto URL command: thunderbird %s ** (evolution:13869): DEBUG: mailto URL program: thunderbird (evolution:13869): e-utils-WARNING **: No parent set, or default parent available for error dialog GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
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 ***