Thank you Sebastien, but the issue I am reporting is not truly a "crash" in that a crash report is not generated. Rather, the network manager simply stops functioning properly and/or responding to inputs. Is there another way to submit this kind of error? - M.
> Date: Mon, 23 May 2016 10:11:02 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1584276] Re: network-manager crashes when changing wireless access points
>
> 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.
> If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_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'.
>
> 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.
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584276
>
> Title:
> network-manager crashes when changing wireless access points
>
> Status in network-manager package in Ubuntu:
> Invalid
>
> 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://dl.dropboxusercontent.com/u/13392425/wireless-info.txt.
>
> 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.16.04.2
> ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
> 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.state:
> [main]
> NetworkingEnabled=true
> WirelessEnabled=true
> WWANEnabled=true
> WimaxEnabled=true
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm-256color
> 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/freedesktop/NetworkManager/Devices/0 dd_wrt (internal) a4d96dd0-91ed-477a-9505-ae1dd6bb5daf /org/freedesktop/NetworkManager/ActiveConnection/0
> eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
> lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- --
> nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1584276/+subscriptions
Thank you Sebastien, but the issue I am reporting is not truly a "crash" in that a crash report is not generated. Rather, the network manager simply stops functioning properly and/or responding to inputs. Is there another way to submit this kind of error? - M.
> Date: Mon, 23 May 2016 10:11:02 +0000 _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'. /bugs.launchpad .net/bugs/ 1584276 /dl.dropboxuser content. com/u/13392425/ wireless- info.txt. 16.04.2 ature: Ubuntu 4.4.0-22.40-generic 4.4.8 state: ed=true =true p/NetworkManage r/Devices/ 0 dd_wrt (internal) a4d96dd0- 91ed-477a- 9505-ae1dd6bb5d af /org/freedeskto p/NetworkManage r/ActiveConnect ion/0 p/NetworkManage r/Devices/ 1 -- -- -- p/NetworkManage r/Devices/ 2 -- -- -- /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1584276/ +subscriptions
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 1584276] Re: network-manager crashes when changing wireless access points
>
> 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.
> 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.
>
> ** Changed in: network-manager (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> network-manager crashes when changing wireless access points
>
> Status in network-manager package in Ubuntu:
> Invalid
>
> 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]
> NetworkingEnabl
> WirelessEnabled
> WWANEnabled=true
> WimaxEnabled=true
> ProcEnviron:
> LANGUAGE=en_US
> TERM=xterm-256color
> 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'.
>
> To manage notifications about this bug go to:
> https:/