GNOME Bugzilla – Bug 430836
crash in System Log: Checking syslog through ...
Last modified: 2007-04-18 00:03:18 UTC
Version: 2.16.1 What were you doing when the application crashed? Checking syslog through gnome graphical application, and switched to firefox to look for specific error code found in syslog. While doing this syslog was probably updated because "syslog" title in the left panel of the frontend became bold, then the graphical application crushed. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 77856768 vsize: 0 resident: 77856768 share: 0 rss: 14405632 rss_rlim: 0 CPU usage: start_time: 1176854041 rtime: 0 utime: 530 stime: 0 cutime:520 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225312064 (LWP 4939)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 128641
Thread 1 (Thread -1225312064 (LWP 4939))
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 355887 ***