GNOME Bugzilla – Bug 357730
crash in Networking: i was confiur
Last modified: 2008-01-08 00:20:02 UTC
Version: 2.15.4 What were you doing when the application crashed? i was confiur Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.0 2006-09-04 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 32108544 vsize: 0 resident: 32108544 share: 0 rss: 11681792 rss_rlim: 0 CPU usage: start_time: 1159238194 rtime: 0 utime: 45 stime: 0 cutime:41 cstime: 0 timeout: 4 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 -1225046352 (LWP 4748)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 73266
Thread 1 (Thread -1225046352 (LWP 4748))
According to the stack trace, this looks like a crash in the ubuntu gtk+ theme. Can you get this crash using a different theme?
*** Bug 359611 has been marked as a duplicate of this bug. ***
I'm not sure what gtk+ theme is, but I changed my Ubuntu Edgy Eft theme preference from LeagcyHuman to Outdoors, I still get the crash. Does this answer your question?
Partially. Outdoors is still an ubuntu-specific theme and likely shares code with LegacyHuman. Could you try clearlooks or crux or glider or one of the other non-ubuntu themes?
Still crashed. I tried three of them mentioned by you. Every time I press 'configure' ethernet interface, it crashed and gave me bug reporting window.
Interesting. Could you attach the stack trace you get with one of the other themes to this bug? Also, could you install debug packages in order to get a stack trace with debugging symbols (see http://live.gnome.org/GettingTraces/DistroSpecificInstructions for more info on how to do so)?
I will do what you suggested me. Actually the whole story is as follows: 1. At first I tried to type my Default Gateway in the System--->Networking menu but the default gateway could not be recorded. 2. I kept repeating the steps by typing the gateway address and pressed OK, open the Networking menu, checked whether or not the gateway has been recorded, still empty, typed the address again, clicked OK 3. Finally at one stage, the networking tools crashed, including the ethernet interface configuration tool. 4. Apparently the blank gateway address is a bug and I had to use terminal to assign the gateway (this bug has been reported by many Ubuntu 6.10 Beta users).
Created attachment 74055 [details] Stack trace using ClearLooks This is the stack trace when using ClearLooks theme. I have installed libglib2.0-0-dbg and so on but still the debugging symbol is not found. I don;t know why.
The stack trace in comment 8 looks nothing like the original stack trace filed with this bug report; I'm pretty sure they represent two different bugs. However, the new stack trace is interesting; there appear to be no duplicates of it in bugzilla. It does have some debugging symbols, but more would be nice. Could you install the pango debug package as well and get a new stack trace?
Created attachment 74128 [details] Stack Trace using ClearLooks 061006 Pango installed, here is the new stack trace.
Could you get a backtrace with "LD_LIBRARY_PATH=/usr/lib/debug gdb network-admin"?
I put the command you wrote above but no stack produced from the backtrace command. It said 'no stack'. Here it is: GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i486-linux-gnu"...(no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (gdb) bt No stack.
You can get the backtrace with: LD_LIBRARY_PATH=/usr/lib/debug gdb network-admin (gdb) run ... get the crash (gdb) thread apply all bt
Created attachment 74348 [details] gdb backtrace network-admin here is the backtrace :), i should have asked you how to do it beforehand :)
Thank you for the work on that, reopening since the backtrace is correct, doesn't look like a g-s-t issue though
Any possible hardware issue from my side?
no, probably a software bug rather
*** Bug 363138 has been marked as a duplicate of this bug. ***
*** Bug 366289 has been marked as a duplicate of this bug. ***
Could someone provide a stacktrace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 75588 [details] Created from System - Administration - Networking
*** Bug 370882 has been marked as a duplicate of this bug. ***
*** Bug 383952 has been marked as a duplicate of this bug. ***
*** Bug 386244 has been marked as a duplicate of this bug. ***
*** Bug 403043 has been marked as a duplicate of this bug. ***
*** Bug 407405 has been marked as a duplicate of this bug. ***
This bug happens not just in gnome-system-tools. Should it be moved to glib/gtk+?
*** Bug 407806 has been marked as a duplicate of this bug. ***
*** Bug 378285 has been marked as a duplicate of this bug. ***
*** Bug 380150 has been marked as a duplicate of this bug. ***
*** Bug 394665 has been marked as a duplicate of this bug. ***
*** Bug 424533 has been marked as a duplicate of this bug. ***
Could someone test with gnome-system-tools 2.18? I suspect this was caused by a memory corruption bug that got fixed during 2.17.x
*** Bug 440033 has been marked as a duplicate of this bug. ***
Closing since nobody else has complained since then