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

2006-03-16 Thread Daniel Holbach
Public bug report changed:
https://launchpad.net/malone/bugs/24242

Changed in: GNOME Nettool (upstream)
 Status: Confirmed = Fix Committed

Comment:
fix in CVS

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


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

2006-03-15 Thread Daniel Holbach
Public bug report changed:
https://launchpad.net/malone/bugs/24242

Changed in: GNOME Nettool (upstream)
 Status: Unconfirmed = Confirmed

Comment:
Upstream has a patch ready.

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


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

2006-03-15 Thread Daniel Holbach
Public bug report changed:
https://launchpad.net/malone/bugs/24242

Task: ubuntu gnome-nettool
   Assignee: Daniel Holbach = Ubuntu Desktop Bugs
 Status: Unconfirmed = Confirmed

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


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

2006-02-11 Thread Firmicus
Public bug report changed:
https://launchpad.net/malone/bugs/24242

Comment:
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:

[EMAIL PROTECTED]:~ # 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.

--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs