gnome-nettool 1.4.1 segfaults when called from the commandline with wrong or incomplete arguments.

[Eric Feliksik]

gnome-nettool 1.4.1 segfaults when called from the commandline with wrong or
incomplete arguments.

Works:
$ gnome-nettool -l www.aap.nl
$ gnome-nettool -p www.aap.nl
$ gnome-nettool --ping=www.aap.nl
$ gnome-nettool --ping=

The latter options pops up a window "a network address was not specified". Nice!

Segmentations fault occur with:
$ gnome-nettool -l
$ gnome-nettool -p
$ gnome-nettool --ping
$ gnome-nettool -help
$ gnome-nettool --random-string

This is not a catastrophic bug, but it's a bug.

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

[Michael Herrmann (michael-herrmann)]

For me gnome-nettool always crashes with the following output:
# gnome-nettool
*** glibc detected *** double free or corruption (out): 0x081f5e00 ***
Abgebrochen

[Daniel Holbach (dholbach)]

Thanks for your bug report. I forwarded the issue to the upstream bug tracker:
http://bugzilla.gnome.org/show_bug.cgi?id=326184

[Firmicus (firmicus)]

I can confirm Michael Herrmann's post. On both my laptop (clean Breezy install) and my desktop (also Breezy), gnome-nettool always instantly segfaults, regardless whether it is called from the gnome menu or the command line. The latter yields:

root@samarqand:~ # gnome-nettool
*** glibc detected *** double free or corruption (out): 0x08297000 ***
Abandon

On both machines I have a running kernel module for a WLAN USB stick (ftp://ftp.avm.de/cardware/fritzwlanusb.stick/linux/suse.10.0/fwlanusb-suse10.0-0.09.00-beta.tar.gz)
which is betaware and may well be the cause of the problem. Indeed I don't think the issue showed up before the WLAN was set up.

[Daniel Holbach (dholbach)]

Upstream has a patch ready.

[Daniel Holbach (dholbach)]

fix in CVS

[Sebastien Bacher (seb128)]

that bug has been fixed for dapper