GNOME Bugzilla – Bug 486743
crash in Tasks: evolution on workspace 1...
Last modified: 2007-10-22 22:22:23 UTC
Version: 2.10 What were you doing when the application crashed? evolution on workspace 1 downloading mail. Me on workspace 4 using firefox. 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Darkilouche Icon Theme: humility-icons-MERGE Memory status: size: 117030912 vsize: 117030912 resident: 22556672 share: 17231872 rss: 22556672 rss_rlim: 4294967295 CPU usage: start_time: 1192430159 rtime: 135 utime: 112 stime: 23 cutime:0 cstime: 0 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 -1208195360 (LWP 3070)] [New Thread -1272976496 (LWP 3584)] [New Thread -1224201328 (LWP 3195)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170272
Thread 1 (Thread -1208195360 (LWP 3070))
----------- .xsession-errors (21 sec old) --------------------- Mon Oct 15 08:50:43 2007 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding Mon Oct 15 08:50:54 2007 CConn: Throughput 6000 kbit/s - changing to hextile encoding CConn: Throughput 6000 kbit/s - changing to full colour CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using hextile encoding kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
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 ***