GNOME Bugzilla – Bug 496391
crash in Tasks: just opened Evoltion and...
Last modified: 2007-11-14 00:53:31 UTC
Version: 2.10 What were you doing when the application crashed? just opened Evoltion and Bug report came up 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 119631872 vsize: 119631872 resident: 37740544 share: 30208000 rss: 37740544 rss_rlim: 4294967295 CPU usage: start_time: 1194947609 rtime: 66 utime: 58 stime: 8 cutime:0 cstime: 1 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 -1208310048 (LWP 2516)] [New Thread -1242567792 (LWP 2542)] [New Thread -1220285552 (LWP 2538)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 177377
Thread 1 (Thread -1208310048 (LWP 2516))
----------- .xsession-errors (52008 sec old) --------------------- ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ** (<unknown>:3302): WARNING **: Failed to send buffer ...Too much output, ignoring rest... --------------------------------------------------
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 ***