NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()

[helboof]

i386 vivid
kernel - 3.18.0-11

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu4
ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
Uname: Linux 3.18.0-11-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.15.1-0ubuntu4
Architecture: i386
CrashCounter: 1
Date: Sun Feb 1 18:03:35 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 2014-12-15 (48 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha i386 (20141214)
IpRoute:
 default via 192.168.24.1 dev eth0
 192.168.24.0/24 dev eth0 proto kernel scope link src 192.168.24.24
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
 WimaxEnabled=true
ProcCmdline: NetworkManager
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
Signal: 5
SourcePackage: network-manager
StacktraceTop:
 ASSERT_VALID_PATH_COMPONENT ()
 nm_utils_ip6_property_path ()
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__OBJECT () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: NetworkManager crashed with signal 5 in ASSERT_VALID_PATH_COMPONENT()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-12-17T21:47:23.164341
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: Error: nmcli (0.9.10.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
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 #1416635, 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.