GNOME Bugzilla – Bug 494982
crash in Tasks:
Last modified: 2007-11-11 12:11:13 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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 147156992 vsize: 147156992 resident: 41078784 share: 32268288 rss: 41078784 rss_rlim: 4294967295 CPU usage: start_time: 1194530929 rtime: 124 utime: 107 stime: 17 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 -1208219936 (LWP 18177)] [New Thread -1272325232 (LWP 18380)] [New Thread -1228878960 (LWP 18355)] [New Thread -1239372912 (LWP 18301)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 176329
Thread 1 (Thread -1208219936 (LWP 18177))
----------- .xsession-errors (7 sec old) --------------------- Checking for GLX_SGIX_fbconfig : passed Checking for GLX_EXT_texture_from_pixmap : passed Checking for non power of two texture support : passed Checking maximum texture size : passed (2048x2048) compiz: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. compiz: No manageable screens found on display :0.0 ** Message: <info> You are now connected to the wired network. ** Message: <info> Activating VPN connection 'Boston'. CalDAV Eplugin starting up ... ** (evolution:18177): DEBUG: mailto URL command: evolution --component=mail %s ** (evolution:18177): 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 364700 ***