GNOME Bugzilla – Bug 456226
crash in System Log: The machine was sitting ...
Last modified: 2007-07-13 19:36:01 UTC
Version: 2.16.1 What were you doing when the application crashed? The machine was sitting idle overnight. The following windows were open: Firefox (3), Screem, System Log Viewer, file manager(2), terminal(2), python(2), OpenOffice Writer, Search for Files, gedit(root), gedit(user). When I activated the System Log View window, it was blank. When I attempted to close the window, the following message box was displayed (The window "/var/log/auth.log (monitored) - System Log Viewer" is not responding. Forcing this application to quit will cause you to lose any unsaved changes.) and I selected 'Force Quit'. I was able to reopen the System Log Viewer, open and browse kern.log; however, when I subsequently attempted to select other logs I had opened in the previous session, the content window was blank; I was able to reselect the kern.log window and see its contents. All other application windows responded normally. I do have the 'random' screensaver enabled. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 71585792 vsize: 0 resident: 71585792 share: 0 rss: 16629760 rss_rlim: 0 CPU usage: start_time: 1184218967 rtime: 0 utime: 170 stime: 0 cutime:162 cstime: 0 timeout: 8 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 -1224619840 (LWP 20248)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 147513
Thread 1 (Thread -1224619840 (LWP 20248))
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 363472 ***