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

[userdce]

something happened

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: network-manager-gnome 0.9.4.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3
Uname: Linux 3.5.0-1-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.2.5-0ubuntu1
Architecture: amd64
Date: Thu Jun 21 15:37:30 2012
ExecutablePath: /usr/bin/nm-connection-editor
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120510)
ProcCmdline: /usr/bin/nm-connection-editor
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5e2f4d1eb0 <g_slist_length+16>: mov 0x8(%rdi),%rdi
 PC (0x7f5e2f4d1eb0) 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 0x00007f5e2f4d1eb0 in g_slist_length () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 #1 0x0000000000411b2a 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 cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (compiz:2582): GConf-CRITICAL **: gconf_client_add_dir: assertion `gconf_valid_key (dirname, NULL)' failed
 (nm-connection-editor:3771): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NMConnectionEditor'

[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 #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.