NetworkManager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

[MaksimKa]

Binary package hint: network-manager

 No additional details

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CRDA: Error: [Errno 2] Нет такого файла или каталога
Date: Fri Apr 15 01:05:51 2011
ExecutablePath: /usr/sbin/NetworkManager
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100915)
IpRoute:
 192.168.0.1 dev ppp0 proto kernel scope link src 192.168.0.2
 169.254.0.0/16 dev ppp0 scope link metric 1000
 default via 192.168.0.1 dev ppp0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 ppp0 no wireless extensions.
Keyfiles: Error: [Errno 2] Нет такого файла или каталога
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SegvAnalysis:
 Segfault happened at: 0x8091a6f: mov 0x38(%eax),%eax
 PC (0x08091a6f) ok
 source "0x38(%eax)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: Upgraded to natty on 2011-04-14 (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 #739284, 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.