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

[Leon]

I was editing a VPN connection just after it was created (one pptp & one openvpn). In the window with the two vpn names it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager-gnome 0.9.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
CrashCounter: 1
Date: Tue Sep 13 23:48:32 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/nm-connection-editor
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110904)
IpRoute:
 default via 192.168.1.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.128
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/bin/nm-connection-editor --show --type vpn
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6d0a854bf0 <g_slist_length+16>: mov 0x8(%rdi),%rdi
 PC (0x7f6d0a854bf0) ok
 source "0x8(%rdi)" (0xaaaaaaaaaaaaaab2) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager-applet
Stacktrace:
 #0 0x00007f6d0a854bf0 in g_slist_length () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1 0x00000000004135aa in _start ()
 No symbol table info available.
StacktraceTop:
 g_slist_length () from /lib/x86_64-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 #848332, 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.