GNOME Bugzilla – Bug 520602
crash in Tasks: Closing the app.
Last modified: 2008-03-06 15:03:03 UTC
Version: 2.10 What were you doing when the application crashed? Closing the app. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 175710208 vsize: 175710208 resident: 84746240 share: 50016256 rss: 84746240 rss_rlim: 4294967295 CPU usage: start_time: 1204752032 rtime: 5350 utime: 3839 stime: 1511 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 -1208895776 (LWP 4103)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 191424
Thread 1 (Thread -1208895776 (LWP 4103))
----------- .xsession-errors (14 sec old) --------------------- package is installed and that the service is running. WeaverThreadLogger: thread (ID: 1) suspended. WeaverThreadLogger: thread (ID: 2) suspended. WeaverThreadLogger: thread (ID: 3) suspended. WeaverThreadLogger: thread (ID: 4) suspended. Weaver dtor: destroying inventory. WeaverThreadLogger: thread (ID: 1) destroyed. WeaverThreadLogger: thread (ID: 2) destroyed. WeaverThreadLogger: thread (ID: 3) destroyed. WeaverThreadLogger: thread (ID: 4) destroyed. Weaver dtor: done X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3a00b67 --------------------------------------------------
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 447591 ***