GNOME Bugzilla – Bug 394667
crash in System Log: Viewing the log in the b...
Last modified: 2007-01-09 22:43:28 UTC
Version: 2.16.1 What were you doing when the application crashed? Viewing the log in the background and issuing a command in a terminal. The keyboard seemed to hang, so I hit it quite hard, I can see now something is wrong with my backspace.... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 55205888 vsize: 0 resident: 55205888 share: 0 rss: 16695296 rss_rlim: 0 CPU usage: start_time: 1168356987 rtime: 0 utime: 81 stime: 0 cutime:77 cstime: 0 timeout: 4 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 -1225226048 (LWP 5210)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 100721
Thread 1 (Thread -1225226048 (LWP 5210))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 355887 ***