network-manager crashes when changing wireless access points
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
After upgrading to 16.04 LTS, whenever trying to switch wifi access points (APs), network-manager "crashes" -- meaning that the applet no longer displays available APs and in their stead is a message "device not ready."
In case it helps, here are the wifi script results: https:/
Note that this is bug different and distinct from Bug #1574347 (wifi dies on wake from suspend), and the reported fix for that bug does not help at all.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri May 20 19:49:10 2016
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2015-05-17 (369 days ago)
InstallationMedia:
IpRoute:
default via 10.0.1.2 dev wlan0 proto static metric 600
10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.99 metric 600
169.254.0.0/16 dev wlan0 scope link metric 1000
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
LANGUAGE=en_US
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to xenial on 2016-04-23 (27 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
wlan0 wifi connected /org/freedeskto
eth0 ethernet unavailable /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 bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit. _my_crash_ report. crash' where _my_crash_ report. crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/ _my_crash_ report. crash'.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.