GNOME Bugzilla – Bug 393757
crash in System Log: Just booted; started sys...
Last modified: 2007-01-07 01:32:09 UTC
Version: 2.16.1 What were you doing when the application crashed? Just booted; started syslog to examine the messages as having trouble with NetworkManager using wpa_supplicant; then started terminal session to find out what 'gconfd' is - not relevant to my probem, but like to know what is happening in startup. It looks like the syslog viewer has crashed. (Personally I'm much more interested in why wpa_supplicant isn't starting up, but I'll get it eventually.) Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 39116800 vsize: 0 resident: 39116800 share: 0 rss: 13672448 rss_rlim: 0 CPU usage: start_time: 1168132408 rtime: 0 utime: 421 stime: 0 cutime:412 cstime: 0 timeout: 9 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 -1225426752 (LWP 4925)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 100058
Thread 1 (Thread -1225426752 (LWP 4925))
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 ***