Ubuntu
gnome-system-tools package

Network-admin cannot set right parameters for static IP connection, or switching locations

Bug #80325 reported by Stefano Costa on 2007-01-17

Affects		Status	Importance	Assigned to	Milestone
	gnome-system-tools (Ubuntu)	Fix Released	Medium	Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

On Feisty, there are problems with latest gnome-system-tools network-admin.

I cannot switch between locations, just because when I try to apply a saved location, it segfaults with

Segmentation fault (core dumped).

Furthermore, the network applet shows settings that are different from those that ifconfig outputs. Running network-config --configure eth1 shows the IP/mask/gateway panel but it has no effect when applied (e.g. the old good bar saying "wait for changes to be applied"), and typed changes have no effect.

A new "roaming mode" checkbox instead of the old "leave this device unconfigured" gets me confused... please help.

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-01-18:

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-system-tools:
assignee:	nobody → desktop-bugs
importance:	Undecided → Medium
status:	Unconfirmed → Needs Info

Revision history for this message

Stefano Costa (steko) wrote on 2007-01-19:

valgrind logs Edit (19.7 KiB, application/x-tar)

valgrind logs attached

Revision history for this message

Brad Johnson (brad-bkjohnson) wrote on 2007-01-31:

I assume "roaming mode" lets network-manager control the interface. Unchecking roaming-mode allows for manual configuration of the interface.

While I haven't had a program crash the network-admin incorrectly writes a static interface declaration in /etc/network/interfaces.

"iface eth0 inet
address xxx.xxx.xxx.xxx
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx

auto eth0"

This entry should be:

"iface eth0 inet static
address xxx.xxx.xxx.xxx
netmask xxx.xxx.xxx.xxx
gateway xxx.xxx.xxx.xxx

auto eth0"

The absence of "static" in the declaration causes network-admin to see the interface as unconfigured. This makes it impossible to configure an interface with a static ip address as network-admin continually shows the interface in "roaming mode". Manually adding "static" to the end of the declaration resolves this behavior.

This bug seems to also be the cause of bug #82088 filed against network-manager.

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-02-03:

The valgrind log points a problem:

==19663== Invalid read of size 1
==19663== at 0x40221E8: strlen (mc_replace_strmem.c:246)
==19663== by 0x49B06AD: g_strdup (in /usr/lib/libglib-2.0.so.0.1200.9)
==19663== by 0x495E899: (within /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x493F215: g_object_set_valist (in /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x493F785: g_object_set (in /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x805142A: (within /usr/bin/network-admin)
==19663== by 0x8051722: (within /usr/bin/network-admin)
==19663== by 0x8053DBA: (within /usr/bin/network-admin)
==19663== by 0x49459C8: g_cclosure_marshal_VOID__VOID (in /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x493862A: g_closure_invoke (in /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x49490F2: (within /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== by 0x494A616: g_signal_emit_valist (in /usr/lib/libgobject-2.0.so.0.1200.9)
==19663== Address 0x1 is not stack'd, malloc'd or (recently) free'd