NetworkManager crashed with SIGSEGV in g_type_instance_get_private()

[HLK]

Happens very often right after login

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.8.9997+git.20110614t173923.b4a72d1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-5.6-generic 3.0.0-rc7
Uname: Linux 3.0.0-5-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Jul 19 13:21:50 2011
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
IpRoute:
 default via 192.168.2.1 dev eth0 proto static
 169.254.0.0/16 dev eth0 scope link metric 1000
 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.5 metric 1
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No such file or directory
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:

SegvAnalysis:
 Segfault happened at: 0x5eb672 <g_type_instance_get_private+34>: mov (%edx),%ecx
 PC (0x005eb672) ok
 source "(%edx)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_type_instance_get_private () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 nm_agent_manager_save_secrets ()
 ?? ()
 ?? ()
 ?? ()
Title: NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
UpgradeStatus: Upgraded to oneiric on 2011-07-19 (0 days ago)
UserGroups:

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