GNOME Bugzilla – Bug 446130
crash in Tasks:
Last modified: 2007-06-12 00:46:19 UTC
What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:47:07 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 576991232 vsize: 576991232 resident: 30744576 share: 16187392 rss: 30744576 rss_rlim: 18446744073709551615 CPU usage: start_time: 1181505338 rtime: 617 utime: 546 stime: 71 cutime:1 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496397920 (LWP 464)] [New Thread 1157925200 (LWP 546)] [New Thread 1147435344 (LWP 505)] (no debugging symbols found) 0x000000307980d89f in waitpid () from /lib64/libpthread.so.0
+ Trace 139864
Thread 1 (Thread 46912496397920 (LWP 464))
----------- .xsession-errors (425750 sec old) --------------------- fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection fixme:xrender:X11DRV_AlphaBlend not a dibsection ...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 334966 ***