NetworkManager crashed with SIGSEGV in g_closure_invoke()

[Stuart Bishop]

Crash after fresh boot to apply latest Vivid updates.

'sudo service NetworkManager restart' got things reconnected.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu13
ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
Uname: Linux 3.19.0-11-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CRDA:
 country SG: DFS-UNSET
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5170 - 5250 @ 40), (N/A, 20), (N/A)
  (5250 - 5330 @ 40), (N/A, 20), (0 ms), DFS
  (5735 - 5835 @ 40), (N/A, 20), (N/A)
CrashCounter: 1
Date: Thu Apr 2 13:02:30 2015
ExecutablePath: /usr/sbin/NetworkManager
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-03-13 (19 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
SegvAnalysis:
 Segfault happened at: 0x487202: mov (%rbx),%rdi
 PC (0x00487202) ok
 source "(%rbx)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%rdi" 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 () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to vivid on 2015-03-16 (16 days ago)
UserGroups:

nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

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