NetworkManager crashes after reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I upgraded my HP Chromebook 14 from 15.04 to 15.10 beta. After cold boot, NetworkManager crashes and I get the popup to send a bug report for a NM crash. There is no network, either. Restarting the NetworkManager service from a terminal fixes the issue ... until next reboot :)
~$ sudo service NetworkManager restart
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu4
ProcVersionSign
Uname: Linux 4.2.0-15-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 9 16:39:39 2015
ExecutablePath: /usr/sbin/
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IpRoute:
default via 10.0.0.1 dev wlan0 proto static metric 600
10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.38 metric 600
169.254.0.0/16 dev wlan0 scope link metric 1000
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: /usr/sbin/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlan0 wifi connected /org/freedeskto
ttyUSB0 gsm disconnected /org/freedeskto
lo loopback unmanaged /org/freedeskto
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
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 #1500399, 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.