GNOME Bugzilla – Bug 361647
crash in Networking: I'm just trying to get t...
Last modified: 2007-01-18 18:21:21 UTC
Version: 2.15.5 What were you doing when the application crashed? I'm just trying to get to network setings GUI application Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 34889728 vsize: 0 resident: 34889728 share: 0 rss: 12374016 rss_rlim: 0 CPU usage: start_time: 1160642450 rtime: 0 utime: 34 stime: 0 cutime:32 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/network-admin' (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 -1225677136 (LWP 5273)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75948
Thread 1 (Thread -1225677136 (LWP 5273))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
*** Bug 365254 has been marked as a duplicate of this bug. ***
*** Bug 371832 has been marked as a duplicate of this bug. ***
*** Bug 373529 has been marked as a duplicate of this bug. ***
*** Bug 373530 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 356180 ***
*** Bug 381125 has been marked as a duplicate of this bug. ***
*** Bug 388590 has been marked as a duplicate of this bug. ***
*** Bug 390739 has been marked as a duplicate of this bug. ***
*** Bug 391870 has been marked as a duplicate of this bug. ***
*** Bug 391882 has been marked as a duplicate of this bug. ***
*** Bug 392746 has been marked as a duplicate of this bug. ***
*** Bug 397351 has been marked as a duplicate of this bug. ***
*** Bug 398043 has been marked as a duplicate of this bug. ***