network-admin crashes (segfaults) on starting

Bug #83421 reported by Phil Housley
2
Affects Status Importance Assigned to Milestone
gnome-system-tools (Ubuntu)
Fix Released
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

The entire output is:

$ sudo network-admin
Segmentation fault (core dumped)

This is on feisty, since at least the herd2 release. Currently version 2.17.5-0ubuntu1. The machine has 3 nics, an rtl 8139, a via rhine and an acx111 wireless, but there are no drivers loaded for the last two. /etc/network/interfaces has nothing at all in except for:

auto lo
iface lo inet loopback

When starting under gdb, I get (amongst the many "no debugging symbols found"s):

...
[New Thread -1226033472 (LWP 8363)]
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1226033472 (LWP 8363)]
0xb75b9ea0 in g_slice_alloc () from /usr/lib/libglib-2.0.so.0

If there is a dbg version of the package, I'll happily try it out

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. The packages have a -dbgysm variant containing the debug symbols you can install, that's described on https://wiki.ubuntu.com/DebuggingProgramCrash. A crash to alloc looks like a memory corruption. Could you try to get a valgrind log (https://wiki.ubuntu.com/Valgrind) for the problem?

Changed in gnome-system-tools:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Phil Housley (undeconstructed) wrote :

Installing the dbgsym version didn't actually give any more gdb output.

Valgrind log is attached as per that wiki page.

Revision history for this message
Sebastien Bacher (seb128) wrote :

The problem seems to happen to pango, could you get a log with libpango1.0-0-dbgsym installed?

Revision history for this message
Phil Housley (undeconstructed) wrote :

Sure.

Revision history for this message
Phil Housley (undeconstructed) wrote :

I think this is totally fixed with 2.17.91-0ubuntu1.

Revision history for this message
Sebastien Bacher (seb128) wrote :

right, that was probably due to the memory corruption which has been fixed with 2.17.91

Changed in gnome-system-tools:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.