GNOME Bugzilla – Bug 362816
crash in Networking: Clicked the "Networking"...
Last modified: 2007-01-19 15:09:28 UTC
Version: 2.15.5 What were you doing when the application crashed? Clicked the "Networking" option under System->Administration. The dialog never shows up. It just goes directly to Bug Buddy. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 28749824 vsize: 0 resident: 28749824 share: 0 rss: 10813440 rss_rlim: 0 CPU usage: start_time: 1161078175 rtime: 0 utime: 34 stime: 0 cutime:31 cstime: 0 timeout: 3 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 -1225750864 (LWP 5510)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 76761
Thread 1 (Thread -1225750864 (LWP 5510))
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!
Hi Sebastien, It seems I have two copies of this bug (see 361617, which can be closed to this ticket.) I'm attaching the new stack trace to this ticket. It should contain the information you were looking for, but, if it doesn't, please let me know. Thanks, Dave Spadea
Created attachment 74988 [details] New stack trace with dbgsym packages installed With dbgsym packages installed, per request.
Thank you for the backtrace. Copying a part of it to a comment to make easier to list duplicates for it "#4 0xb71fe6a8 in strcmp () from /lib/tls/i686/cmov/libc.so.6
+ Trace 77113
*** Bug 361617 has been marked as a duplicate of this bug. ***
*** Bug 364825 has been marked as a duplicate of this bug. ***
confirming as per duplicates.
I don't know if this bit of trivia helps at all or not, but I just upgraded an Ubuntu Dapper box to Edgy, and this bug does not happen. The machine I'm having trouble with is a box that was installed with Edgy and received the subsequent updates. I haven't rebooted the other box yet, so that may be a reason that I don't hit the bug, but I've logged out/in and am running the new GNOME. I plan to reboot the box on Friday evening. I'll let you know whether this bug starts happening at that point. I hope this helps to narrow down the possible causes. Otherwise, sorry for the extra noise.
*** Bug 365371 has been marked as a duplicate of this bug. ***
*** Bug 365475 has been marked as a duplicate of this bug. ***
*** Bug 367548 has been marked as a duplicate of this bug. ***
*** Bug 367643 has been marked as a duplicate of this bug. ***
*** Bug 367956 has been marked as a duplicate of this bug. ***
*** Bug 367962 has been marked as a duplicate of this bug. ***
*** Bug 373124 has been marked as a duplicate of this bug. ***
bug 371657 could be a dup
*** Bug 373710 has been marked as a duplicate of this bug. ***
*** Bug 371657 has been marked as a duplicate of this bug. ***
*** Bug 374404 has been marked as a duplicate of this bug. ***
*** Bug 374405 has been marked as a duplicate of this bug. ***
*** Bug 374573 has been marked as a duplicate of this bug. ***
On my box I have noticed that this bug (if it is indeed the same) does not happen when I start network-admin from the command line. However I do not get the "networks configurations" that I had saved (those that appear in the drop down box on top of the dialog). This might be perfectly normal, as I am probably missing an environment variable, but this makes me think that these saved network settings might be the cause of the crash.
*** This bug has been marked as a duplicate of 364430 ***
*** Bug 379135 has been marked as a duplicate of this bug. ***
*** Bug 387826 has been marked as a duplicate of this bug. ***
*** Bug 388725 has been marked as a duplicate of this bug. ***
*** Bug 389248 has been marked as a duplicate of this bug. ***
*** Bug 398326 has been marked as a duplicate of this bug. ***