GNOME Bugzilla – Bug 392926
crash in System Log: looking at system status
Last modified: 2007-01-04 23:14:29 UTC
Version: 2.16.0 What were you doing when the application crashed? looking at system status Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 87416832 vsize: 0 resident: 87416832 share: 0 rss: 9838592 rss_rlim: 0 CPU usage: start_time: 1167951735 rtime: 0 utime: 14 stime: 0 cutime:9 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/sbin/gnome-system-log' (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 -1209014576 (LWP 3149)] (no debugging symbols found) 0x009f8402 in __kernel_vsyscall ()
+ Trace 99457
Thread 1 (Thread -1209014576 (LWP 3149))
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 366458 ***