GNOME Bugzilla – Bug 491609
crash in Tasks:
Last modified: 2007-10-30 10:25:08 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.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: Bluecurve Icon Theme: Bluecurve Memory status: size: 167944192 vsize: 167944192 resident: 58142720 share: 51601408 rss: 58142720 rss_rlim: 4294967295 CPU usage: start_time: 1193719900 rtime: 182 utime: 163 stime: 19 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 -1208826144 (LWP 2985)] [New Thread -1263535216 (LWP 3063)] [New Thread -1274025072 (LWP 3010)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173830
Thread 1 (Thread -1208826144 (LWP 2985))
----------- .xsession-errors (49 sec old) --------------------- Tue Oct 30 10:23:52 2007 CConn: connected to host 172.16.0.12 port 5900 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 Tue Oct 30 10:24:00 2007 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 8 (8bpp) colour-map CConn: Using ZRLE encoding CConn: Throughput 20000 kbit/s - changing to hextile encoding CConn: Using hextile encoding Tue Oct 30 10:27:00 2007 main: End of stream --------------------------------------------------
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 ***