I've seen this too since I upgraded from 11.10 to 12.04 (never experienced this prior to 12.04). I would add that it is not just the VPN Connections submenu that stops working; it's any entry in the applet's menu that stops working. When this happens, the workaround that I use is:
kill -1 `pidof nm-applet`
nm-applet &
I usually see this problem after several suspend-resume cycles while commuting between home and work. It could have something to do with new wireless networks being detected so it is probably not the suspend-resume cycles themselves but the constant scanning and discovery of wireless networks that is associated with suspending the machine in one place and then resuming in some other place. I can try to run with wireless disabled (via the nm-applet option for this) for a few days to see if the problem reoccurs.
I've read about previous memory leaks in nm-applet possibly causing this but I have been monitoring memory utilization of the nm-applet process and I have not noticed a huge utilization when the applet is in an unresponsive state.
If anyone finds the master bug please lets us know so we can subscribe to it.
I've seen this too since I upgraded from 11.10 to 12.04 (never experienced this prior to 12.04). I would add that it is not just the VPN Connections submenu that stops working; it's any entry in the applet's menu that stops working. When this happens, the workaround that I use is:
kill -1 `pidof nm-applet`
nm-applet &
I usually see this problem after several suspend-resume cycles while commuting between home and work. It could have something to do with new wireless networks being detected so it is probably not the suspend-resume cycles themselves but the constant scanning and discovery of wireless networks that is associated with suspending the machine in one place and then resuming in some other place. I can try to run with wireless disabled (via the nm-applet option for this) for a few days to see if the problem reoccurs.
I've read about previous memory leaks in nm-applet possibly causing this but I have been monitoring memory utilization of the nm-applet process and I have not noticed a huge utilization when the applet is in an unresponsive state.
If anyone finds the master bug please lets us know so we can subscribe to it.