GNOME Bugzilla – Bug 495407
crash in Tasks: checking email, i don't ...
Last modified: 2007-11-11 12:45:22 UTC
Version: 2.10 What were you doing when the application crashed? checking email, i don't even use the Tasks application, it is automatically part of Evolution 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 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 762040320 vsize: 762040320 resident: 86425600 share: 67141632 rss: 86425600 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194617748 rtime: 1592 utime: 1463 stime: 129 cutime:0 cstime: 0 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 46912496481648 (LWP 5232)] [New Thread 1136945488 (LWP 7500)] [New Thread 1084229968 (LWP 5294)] [New Thread 1105475920 (LWP 5284)] (no debugging symbols found) 0x000000363080d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 176648
Thread 2 (Thread 1136945488 (LWP 7500))
----------- .xsession-errors (3504 sec old) --------------------- (nautilus:5096): libgnomevfs-CRITICAL **: expand_macro: assertion `uris != NULL' failed (nautilus:5096): libgnomevfs-CRITICAL **: expand_macro: assertion `uris != NULL' failed (nautilus:5096): libgnomevfs-CRITICAL **: expand_macro: assertion `uris != NULL' failed kbuildsycoca running... DCOP Cleaning up dead connections. Failed to load Main-Class manifest attribute from /media/disk/servlet.jar closing Model not found, discarding config ** (gedit:7264): WARNING **: could not set the value of Settings.Document.Filter, node not found ** (gedit:7264): WARNING **: could not set the value of Settings.Document.Filter, node not found --------------------------------------------------
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 445309 ***