[network-admin] Crash when starting from menu.

Thanks for your bug. Do you have the same issue if you run it from a command line? Could you install libglib2.0-0-dbg and get a backtrace with gdb?
- gdb network-admin
(gdb) run
... get the crash
(gdb) thread apply all bt

I have the same issue when i run it from command line as normal user. With sudo or gksudo it works without problems (as far as i can see). I will make a backtrace tonight when i'm on my system again.

Here is the bug report made for Gnome-bugzilla

http://bugzilla.gnome.org/show_bug.cgi?id=364625

Here is all the gdb output i get

jeroen@lisa-ubuntu:~$ gdb network-admin
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) run
Starting program: /usr/bin/network-admin
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225529680 (LWP 5091)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1225529680 (LWP 5091)]
IA__g_slice_free_chain_with_offset (mem_size=12, mem_chain=0x829edd0,
    next_offset=4) at gslice.c:858
858 gslice.c: No such file or directory.
        in gslice.c
(gdb) thread apply all bt

Thread 1 (Thread -1225529680 (LWP 5091)):
#0 IA__g_slice_free_chain_with_offset (mem_size=12, mem_chain=0x829edd0,
    next_offset=4) at gslice.c:858
#1 0xb75eb891 in IA__g_list_free (list=0x829edd0) at glist.c:53
#2 0x08050ba7 in ?? ()
#3 0x0829edd0 in ?? ()
#4 0x0804e4dc in gtk_combo_box_set_active_iter@plt ()
#5 0x00000000 in ?? ()

I am also having the exact same problem. I traced the Gnome-bugzilla report, and the power that be claim it is not Gnome related problem. So what is it?? I cannot connect to wireless devices because it crashes. running via terminal using gksudo or sudo works, but connection to wireless is not even attempted by the tool... it just doesn't work. connection via Ethernet cable works fine as far as I can tell. I received similar feed back as you posted above so i do not see the point of posting that, however, I am trying to get this issue higher than moderate, because the tool itself seems to be broken.

it's probably pointing to the wrong upstream bug. Maybe you could get a debug backtrace?

Well I reinstalled the OS, and have yet to see this issue pop up as of yet.

On 10/31/06, Sebastien Bacher <email address hidden> wrote:
>
> it's probably pointing to the wrong upstream bug. Maybe you could get a
> debug backtrace?
>
> --
> [network-admin] Crash when starting from menu.
> https://launchpad.net/bugs/67936
>

no update, closing the bug now. Feel free to reopen with the asked details if you you get that problem again

I thought i've made a debug backtrace. I've posted it here. What do you want me to check, because the problem is still there?

could you get one with gnome-system-tools-dbgsym installed?

I've had the same problem.
Network-admin began to crash at the startup after I've added an host. Removing manually the relative line in /etc/host made network-admin to start again.
Then I've tried to repeat the experiment: adding an host (using network-admin or editing manually the file) makes network-admin to crash at startup.
Hope it helps.

I have found a site claiming to have Razer Tarantula 2.01 drivers.
http://www.razerblueprints.net/index.php?option=com_docman&task=cat_view&gid=60&Itemid=69
I doubt this is legitimate and wanted to know what the deal is, spoof or
virus I dunno.

On 12/24/06, montag <email address hidden> wrote:
>
> I've had the same problem.
> Network-admin began to crash at the startup after I've added an host.
> Removing manually the relative line in /etc/host made network-admin to start
> again.
> Then I've tried to repeat the experiment: adding an host (using
> network-admin or editing manually the file) makes network-admin to crash at
> startup.
> Hope it helps.
>
> --
> [network-admin] Crash when starting from menu.
> https://launchpad.net/bugs/67936
>

The problem still occurs. I tried to install gnome-system-tools-dbgsym, but it wont because it depends on gnome-system-tools (= 2.15.5-0ubuntu2) but i have the ubuntu4 version installed. Should i fall back to version ubuntu2 or wait for an update on the dbgsym package?

getting a backtrace with 0ubuntu2 is fine

This bug should be reopened - description from montag (https://launchpad.net/ubuntu/+source/gnome-system-tools/+bug/67936/comments/11) is correct. After adding entries to /etc/hosts starting network-admin from menu (or from command line) results in application crash. You can successfully run network-admin using sudo/gksudo but this is hardly solution...

Could anybody having the problem get a debug backtrace and valgrind log (https://wiki.ubuntu.com/Valgrind) then we can reopen the bug, without those informations the bug is not that useful

I have to note that i have added 2 lines to /etc/hosts and that since a short time i even get a crash when i run network-admin with sudo or gksudo.

That new crash file looks like http://bugzilla.gnome.org/show_bug.cgi?id=372697 upstream, the valgrind log points no error though. What lines did you add to /etc/hosts to trigger the crash?

Reopening, that doesn't crash with that host extra lines on my box, the bug looks like a memory corruption, nothing obvious to the valgrind log though. Could you try to get an another valgrind log with "G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind..."?

fixed upstream

That upload fixes the problem:

 gnome-system-tools (2.17.91-0ubuntu1) feisty; urgency=low
 .
   * New upstream version:
     Network:
     - Avoid a critical warning
     - Fix invalid memory free() which was causing lots of grief
       (Ubuntu: #67936, #70756)
     - call g_thread_init() to avoid GSlice warning
     - Improve migration of older parameters in location files to newer format
     Shares:
     - Check whether there's connection to the bus before requesting data
       in the nautilus extension
     - call g_thread_init() to avoid GSlice warning
     Time:
     - updated screenshots for the documentation (Ubuntu: #83006)
     Users:
     - Mark a few dialogs as transient for another ones
   * debian/patches/98_automake.dpatch:
     - updated

I'm sorry to post this here, but this issue is threatening my use of Linux as a desktop OS. If I cannot make hosts entries I cannot do my job and my company will revoke my freedom of OS.

So, being new to this I have ask, "can I install http://packages.ubuntulinux.org/feisty/gnome/gnome-system-tools on Ubuntu 6.10 - the Edgy Eft?" Based on the comment from Sebastien Bacher the problem I'm experiencing has been fixed and is no longer a concern for the team. But, for those of us using the "stable release" what can we do?

I have the same problem too, on Ubuntu 6.10, kernel 2.6.17-11.
Today I tried to change th entwork config through system->admin->networking and puff no way to enter in!
I think that it's not feasible to change everytime it using the sys console...
Unfortunatley I can't solve my bug since the gnome-system-tools for my version of Ubuntu is not updated! (version 2.15 or something)
Well it's frustrating this situation! Last time I got a similar issue I was using Windows 95..

I have found that given enough reboots I can always get my system on my home (wifi) or work (ethernet with lots of search domains and hosts entries) networks. I simply have to (usually when I get home from work) delete all the custom entries from /etc/hosts and reboot. Then network-admin will launch okay.

I think one solution would be to make a backup of your base hosts file (no extra entries, just the ones ubuntu put there), and write a shell script like:
#!/bin/sh
## restore_hosts.sh restores the /etc/hosts file to curcumvent
## the bug: https://launchpad.net/ubuntu/+source/gnome-system-tools/+bug/67936
cp -f /etc/hosts.bak /etc/hosts

Then maybe make the script run on boot, or run on Gnome start up. I don't know if the Gnome startup would be too late to avoid the problem. I've never done the former task, but I think you just put the shell script in /etc/init.d/ and symlink to in from the proper runlevel. (/etc/rc[X].d/ where [X] is your default runlevel) based on:
"man runlevel" and calling runlevel on my machine which I consider to be standard Ubuntu, you would use:
sudo ln -s /etc/init.d/restore_hosts.sh /etc/rc2.d/S10restore_hosts.sh

Since gdm is linked as /etc/rc2.d/S13gdm

Hope that helps.

As far as comparing to Windows 95, imagine how many issues Windows 95 would have had if it were developed by free time hobbyists.

The feisty package is not easy to use on edgy, the patch can be used to fix the edgy package though, if somebody want to look at what upstream change fixed that exactly and if it works on edgy we might consider a stable update

On 3/7/07, Sebastien Bacher <email address hidden> wrote:
> The feisty package is not easy to use on edgy, the patch can be used to
> fix the edgy package though, if somebody want to look at what upstream
> change fixed that exactly and if it works on edgy we might consider a
> stable update
>
> --
> [network-admin] Crash when starting from menu.
> https://launchpad.net/bugs/67936
>

Unfortunately I've never done that sort of thing. My end goal is to
be a code contributing member of the Linux community. (At this point
I just offer shell scripts and configuration changes to the KnoppMyth
project.) I will try to do this as my first delve into contributing
code if I may lean on you as a resource.

I'm currently playing with the source code of a simple project
http://freshmeat.net/projects/dbf/?branch_id=32890 to add a few
features. I can make sense of the code and my changes compile fine
and work as expected. It was going to be my first code submission,
but this network-admin thing has greater impact/visibility.

So, knowing this, would you be willing to "bring me into the circle"
so to speak?

--
.!# RichardBronosky #!.

You can start with the MOTU team: https://wiki.ubuntu.com/MOTU. The change that fixed the bug upstream: http://svn.gnome.org/viewcvs/gnome-system-tools?view=rev&revision=3765, testing that change on the edgy package and confirming it fixes the bug would be useful

Okay, I got the specified revision. I compared it to the result of
`apt-get source gnome-system-tool` and have applied only the
"relevant?" changes. But, I'm not sure what to do with it now. I
don't know whether to run the configure script, or use the Makefile
that was in the src, or whether to create a deb (which I've never
done) and use dpkg on it.

Please advise.

Could you try that debdiff? That's the changes from upstream quickly applied without the connection.c modifications which don't apply

If you have questions on how to do changes the MOTU team is the right place, the team has already load to do and using comments for questions doesn't work nicely

Ok, I have made the work around work...lol

and my wifi is dhcp, all i needed to get it working was the wep key.