GNOME Bugzilla – Bug 389390
crash in System Log: I did the command "sudo ...
Last modified: 2006-12-25 09:08:27 UTC
Version: 2.16.1 What were you doing when the application crashed? I did the command "sudo gedit /etc/syslog.conf" I was looking at my syslog.conf ( nothing more ) I then went to bed but locking my station before then I woke up and I see this bug reporting tool Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 37613568 vsize: 0 resident: 37613568 share: 0 rss: 14495744 rss_rlim: 0 CPU usage: start_time: 1167003497 rtime: 0 utime: 1419 stime: 0 cutime:1249 cstime: 0 timeout: 170 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 -1224718672 (LWP 4995)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 96817
Thread 1 (Thread -1224718672 (LWP 4995))
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 355887 ***