GNOME Bugzilla – Bug 394403
crash in Networking: I ran /etc/init.d/networ...
Last modified: 2007-06-18 22:13:50 UTC
Version: 2.15.5 What were you doing when the application crashed? I ran /etc/init.d/networking restart, and hit Ctrl-C before it had completed listening for a DHCP address (DHCPDISCOVER) then ifconfig did not list the interface. At this point I ran Networking. So when it started, there was an interface in limbo, which it did not expect. Maybe it could wait or cancel the DHCP process. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 34402304 vsize: 0 resident: 34402304 share: 0 rss: 11935744 rss_rlim: 0 CPU usage: start_time: 1163878796 rtime: 0 utime: 64 stime: 0 cutime:62 cstime: 0 timeout: 2 it_real_value: 0 frequency: 1 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 -1225169232 (LWP 30124)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 100552
Thread 1 (Thread -1225169232 (LWP 30124))
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 400250 has been marked as a duplicate of this bug. ***
*** Bug 411121 has been marked as a duplicate of this bug. ***
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 356180 ***