nm-connection-editor crashed with SIGSEGV in g_slist_length()

[Yann Dìnendal]

apport notification when I was in the networks connections manager.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager-gnome 0.9.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Date: Sat Sep 24 21:12:58 2011
ExecutablePath: /usr/bin/nm-connection-editor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
IpRoute:
 default via 192.168.0.254 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.11
Keyfiles: Error: [Errno 2] Aucun fichier ou dossier de ce type
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x316540 <g_slist_length+16>: mov 0x4(%edx),%edx
 PC (0x00316540) ok
 source "0x4(%edx)" (0xaaaaaaae) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager-applet
Stacktrace:
 #0 0x00316540 in g_slist_length () from /lib/i386-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1 0x08056d46 in _start ()
 No symbol table info available.
StacktraceTop:
 g_slist_length () from /lib/i386-linux-gnu/libglib-2.0.so.0
 _start ()
Title: nm-connection-editor crashed with SIGSEGV in g_slist_length()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #778355, 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.