NetworkManager crashed with SIGSEGV in g_closure_invoke()

[Piranna]

Binary package hint: network-manager

Happened at boot after just login.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CRDA: Error: [Errno 2] No existe el fichero o el directorio
CrashCounter: 1
Date: Thu Mar 31 18:43:21 2011
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
IpRoute:
 192.168.102.0/24 dev eth0 proto kernel scope link src 192.168.102.137 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.102.80 dev eth0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Keyfiles: Error: [Errno 2] No existe el fichero o el directorio
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcCmdline: NetworkManager
ProcEnviron: PATH=(custom, no user)
RfKill:

SegvAnalysis:
 Segfault happened at: 0x44c07c: mov 0x68(%rax),%rax
 PC (0x0044c07c) ok
 source "0x68(%rax)" (0x00000068) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_by_name () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-03-29 (2 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 #737713, 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.