network-admin crashed with SIGSEGV in g_closure_invoke()

Bug #207963 reported by Antti Luoma
12
Affects Status Importance Assigned to Milestone
GST
Fix Released
Critical
gnome-system-tools (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-tools

tried to change eth1 properties

ProblemType: Crash
Architecture: amd64
Date: Thu Mar 27 22:33:09 2008
Disassembly: 0x2:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/network-admin
Package: gnome-system-tools 2.22.0-0ubuntu3
PackageArchitecture: amd64
ProcCmdline: network-admin
ProcCwd: /
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-system-tools
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit_by_name ()
Title: network-admin crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.24-12-xen x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin mythtv plugdev video
SegvAnalysis:
 Segfault happened at: 0x2:
 PC (0x00000002) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA

Revision history for this message
Antti Luoma (anluoma) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
IA__g_closure_invoke (closure=0xb4a290, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x678930, detail=0, instance=0xb9dbd0,
IA__g_signal_emit_valist (instance=0xb9dbd0, signal_id=<value optimized out>,
IA__g_signal_emit_by_name (instance=0xb9dbd0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gnome-system-tools:
status: Incomplete → Invalid
Revision history for this message
Vojtěch Látal (vojtik) wrote :

My steps to reproduce this bug are following:
1) In terminal write 'network-admin' or alternatively click 'Network' in menu
2) Click 'Unlock' button and enter your password in order to gain superuser privileges
3) Click 'Hosts' tab
4) Click one of the hosts lines
5) And finally click 'Properties'

Then network-admin crashes.

My hosts file is standard one. Only added some space-separated names for 127.0.0.1

I'm using Intrepid 8.10.

Changed in gnome-system-tools:
status: Invalid → New
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Here is the backtrace. I installed all possible debug symbols.

Changed in gnome-system-tools:
status: New → Confirmed
Changed in gst:
status: Unknown → New
Changed in gnome-system-tools:
status: Confirmed → Triaged
Kees Cook (kees)
description: updated
Revision history for this message
Milan Bouchet-Valat (nalimilan) wrote :

Fixed in Karmic since August.

Changed in gnome-system-tools (Ubuntu):
status: Triaged → Fix Released
Changed in gst:
importance: Unknown → Critical
status: New → 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.