GNOME Bugzilla – Bug 493557
crash in Tasks: start up
Last modified: 2008-03-25 14:19:09 UTC
Version: 2.10 What were you doing when the application crashed? start up 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-10.fc7 #1 SMP Fri Oct 19 14:35:28 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Bluecurve Memory status: size: 611897344 vsize: 611897344 resident: 53714944 share: 43417600 rss: 53714944 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194218454 rtime: 56 utime: 50 stime: 6 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 46912636806496 (LWP 5373)] [New Thread 1231087952 (LWP 5391)] [New Thread 1147169104 (LWP 5382)] [New Thread 1126189392 (LWP 5380)] [New Thread 1105209680 (LWP 5378)] [New Thread 1084229968 (LWP 5376)] (no debugging symbols found) 0x00002aaaacdc997f in waitpid () from /lib64/libpthread.so.0
+ Trace 175257
Thread 1 (Thread 46912636806496 (LWP 5373))
----------- .xsession-errors (14063 sec old) --------------------- localuser:jbrutto being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2763 Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5c specified for 0x12015af (). Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000091 (VLC media ) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Warning: The encoding 'UTF-8' is not supported by the Java runtime. Warning: The encoding 'UTF-8' is not supported by the Java runtime. --------------------------------------------------
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 ***