GNOME Bugzilla – Bug 471408
crash in Tasks:
Last modified: 2007-09-21 18:51:38 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.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Bluecurve Icon Theme: Bluecurve Memory status: size: 269705216 vsize: 269705216 resident: 96649216 share: 67395584 rss: 96649216 rss_rlim: 4294967295 CPU usage: start_time: 1188316389 rtime: 15436 utime: 14627 stime: 809 cutime:36 cstime: 10 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 -1208355104 (LWP 7849)] [New Thread -1420239984 (LWP 11906)] [New Thread -1399260272 (LWP 8065)] [New Thread -1299477616 (LWP 7873)] [New Thread -1288537200 (LWP 7871)] (no debugging symbols found) 0x0014b402 in __kernel_vsyscall ()
+ Trace 158740
Thread 1 (Thread -1208355104 (LWP 7849))
----------- .xsession-errors (9282 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/jacob (nautilus:9489): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Adobe Read) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (gedit:9484): WARNING **: Throbber animation not found ** (gedit:10201): WARNING **: Throbber animation not found ** Message: <info> You are now connected to the wireless network 'Technetium-g'. ** (gedit:11285): WARNING **: Throbber animation 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 467763 ***