GNOME Bugzilla – Bug 505651
crash in Tasks: sufing
Last modified: 2007-12-26 19:54:31 UTC
Version: 2.10 What were you doing when the application crashed? sufing 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.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 158588928 vsize: 158588928 resident: 73150464 share: 42606592 rss: 73150464 rss_rlim: 4294967295 CPU usage: start_time: 1198632846 rtime: 2080 utime: 1811 stime: 269 cutime:158 cstime: 64 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 -1208359200 (LWP 32634)] [New Thread -1233036400 (LWP 32755)] [New Thread -1276454000 (LWP 32676)] [New Thread -1254016112 (LWP 32674)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183049
Thread 1 (Thread -1208359200 (LWP 32634))
----------- .xsession-errors (137 sec old) --------------------- localuser:tiffany being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/31609 compiz: No stencil buffer. Clipping of transformed windows is not going to be correct when screen is transformed. MozPlugger: Error: Failed to execute m4. MozPlugger: Error: Failed to execute m4. CalDAV Eplugin starting up ... evolution-shell-Message: Killing old version of evolution-data-server... ** (evolution:32634): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:32634): DEBUG: mailto URL program: evolution --------------------------------------------------
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 467763 ***