GNOME Bugzilla – Bug 422248
crash in System Log: Looking through system l...
Last modified: 2007-03-24 13:34:24 UTC
Version: 2.16.1 What were you doing when the application crashed? Looking through system log for clues as to why wireless does not work. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 63664128 vsize: 0 resident: 63664128 share: 0 rss: 14061568 rss_rlim: 0 CPU usage: start_time: 1174731624 rtime: 0 utime: 377 stime: 0 cutime:352 cstime: 0 timeout: 25 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 -1225369408 (LWP 18437)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 121739
Thread 1 (Thread -1225369408 (LWP 18437))
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 ***