nm-applet side menus stop working
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
The Network Manager applet shows side menus for "More networks" and "VPN Connections". On occasion, the applet loses the ability to display those options usefully. When in this state, mousing over those menu options causes an empty menu to show up instead of the extra wireless networks or the VPN options, respectively.
"killall nm-applet" followed by "nm-applet --sm-disable &" in a terminal brings back those side menus.
As far as I can tell, Network Manager itself is not affected by this; i.e. any VPN I have up at the time remains operational. Of course, it's difficult to start a new VPN or shut down any running VPN without the menu options to do so.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Fri Jun 15 11:56:09 2012
EcryptfsInUse: Yes
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 192.168.50.2 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.50.0/24 dev eth0 proto kernel scope link src 192.168.50.222 metric 1
192.168.50.0/24 dev wlan0 proto kernel scope link src 192.168.50.106 metric 2
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-
UpgradeStatus: Upgraded to precise on 2012-05-02 (44 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected /org/freedeskto
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled enabled enabled disabled
Status changed to 'Confirmed' because the bug affects multiple users.