[network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()

[dmiranda]

gnome control center crashed when editing network conections

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Mon Feb 27 23:15:27 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: gnome-control-center network
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1349b3e: mov 0x4(%ecx),%eax
 PC (0x01349b3e) ok
 source "0x4(%ecx)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2012-01-17 (42 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.2-0ubuntu2
 deja-dup 21.90-0ubuntu1
 gnome-bluetooth 3.2.2-0ubuntu2
 indicator-datetime 0.3.90-0ubuntu1

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #908670, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.