NetworkManager crashed with SIGSEGV in g_type_instance_get_private()

[Сергей]

I don't know

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: network-manager 0.9.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic x86_64
Architecture: amd64
CRDA: Error: [Errno 2] Нет такого файла или каталога
Date: Thu Sep 1 00:22:36 2011
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831)
IpRoute:
 default via 212.220.34.210 dev ppp0 proto static
 169.254.0.0/16 dev ppp0 scope link metric 1000
 192.168.1.0/24 dev ppp0 proto kernel scope link src 192.168.1.2
 212.220.34.210 dev ppp0 proto kernel scope link src 31.162.96.36
Keyfiles: Error: [Errno 2] Нет такого файла или каталога
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SegvAnalysis:
 Segfault happened at: 0x7fca3ad317c1 <g_type_instance_get_private+33>: cmpq $0x0,(%rdi)
 PC (0x7fca3ad317c1) ok
 source "$0x0" ok
 destination "(%rdi)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 g_type_instance_get_private () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 nm_agent_manager_save_secrets ()
 ?? ()
 ?? ()
 ?? ()
Title: NetworkManager crashed with SIGSEGV in g_type_instance_get_private()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2011-09-01T00:22:36.096509

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