GNOME Bugzilla – Bug 469847
crash in Tasks:
Last modified: 2007-09-24 16:16:39 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.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 646344704 vsize: 646344704 resident: 59035648 share: 34476032 rss: 59035648 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187948235 rtime: 1460 utime: 1338 stime: 122 cutime:34 cstime: 21 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 46912496410768 (LWP 3914)] [New Thread 1136945488 (LWP 4503)] [New Thread 1105475920 (LWP 4501)] [New Thread 1084229968 (LWP 4431)] [New Thread 1094986064 (LWP 3992)] [New Thread 1094719824 (LWP 3986)] (no debugging symbols found) 0x000000339c00d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 157562
Thread 1 (Thread 46912496410768 (LWP 3914))
----------- .xsession-errors (105 sec old) --------------------- VNC Viewer Free Edition 4.1.2 for X - built Jun 11 2007 09:44:37 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Fri Aug 24 11:45:26 2007 CConn: connected to host localhost port 5900 CConnection: Server supports RFB protocol version 3.3 CConnection: Using RFB protocol version 3.3 TXImage: Using default colormap and visual, TrueColor, depth 24. CConn: Using pixel format depth 6 (8bpp) rgb222 CConn: Using ZRLE encoding /bin/bash: play: command not found Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x40000a5 (INBOX (8 t) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find *** This bug has been marked as a duplicate of 465117 ***