NetowrkManager does not connect/diconnect/reconnect randomly

[Aleksandr Panzin]

Upgraded from 12.10 hoping that this issue would be fixed.

After some time being connected to a WiFi network, network manager indicator will stop responding to commands - disconnect, connect and "Edit connections...". A restart/logout helps, but the indicator stops showing the actual signal strength, what network I'm connected to(and the notification says - "Connected to (none)") and will not allow to connect to another network unless WiFi is turned off via RFKill.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: network-manager 0.9.8.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Sat May 4 16:12:29 2013
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2012-10-31 (184 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IpRoute:
 default via 192.168.43.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.241 metric 9
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to raring on 2013-04-23 (11 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.8.0 connected enabled enabled enabled enabled disabled

[Bryan Quigley (bryanquigley)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates.

I'm going to close this bug report as their is nothing else we can do with this old report in a now unsupported version of Ubuntu. If you still have this issue on Ubuntu 14.04 or higher, please do reopen or report a new bug.