GNOME Bugzilla – Bug 459892
crash in Tasks: I asked Evolution to qui...
Last modified: 2007-07-29 14:18:55 UTC
Version: 2.10 What were you doing when the application crashed? I asked Evolution to quit. 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-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 113737728 vsize: 113737728 resident: 36098048 share: 25661440 rss: 36098048 rss_rlim: 4294967295 CPU usage: start_time: 1185280574 rtime: 347 utime: 320 stime: 27 cutime:219 cstime: 24 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 -1208412448 (LWP 5601)] [New Thread -1220633712 (LWP 7275)] [New Thread -1252504688 (LWP 5665)] [New Thread -1295430768 (LWP 5664)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 150218
Thread 2 (Thread -1220633712 (LWP 7275))
----------- .xsession-errors (9330 sec old) --------------------- refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCullAndDraw invalid enumerant refresh: ssgCul ...Too much output, ignoring rest... --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 445309 ***