GNOME Bugzilla – Bug 486515
crash in Tasks:
Last modified: 2007-10-14 13:15:54 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 145440768 vsize: 145440768 resident: 42209280 share: 34484224 rss: 42209280 rss_rlim: 4294967295 CPU usage: start_time: 1192352485 rtime: 124 utime: 106 stime: 18 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209084192 (LWP 14322)] [New Thread -1303131248 (LWP 14358)] [New Thread -1211184240 (LWP 14352)] [New Thread -1262617712 (LWP 14347)] [New Thread -1221674096 (LWP 14345)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 170105
Thread 1 (Thread -1209084192 (LWP 14322))
----------- .xsession-errors --------------------- Network sensor: can not find ath0 /bin/bash: acpitool: command not found X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 158 Minor opcode: 6 Resource id: 0x71 Network sensor: can not find ath0 /bin/bash: acpitool: command not found Network sensor: can not find ath0 /bin/bash: acpitool: command not found ath0 No such device Network sensor: can not find ath0 ath0: error fetching interface information: Device not found /bin/bash: acpitool: command 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 364700 ***