At random times NM applet menu stops responding

It has just happened WITHOUT suspending and resuming.
It was working fine, after a reboot; then I disconnected and reconnected many times, to different networks, and it was working; and after a long time, when trying to disconnect and reconnect to a different network, the issue appeared.

Status changed to 'Confirmed' because the bug affects multiple users.

I have the exact same issue. Also wondering if it might have to do with suspend / resume. I'll try to get some output logs from running nm-applet manually and grabbing log output.

I have had it every since the 11.10 Unity release. It affects menus and non-Unity system tray icon menus also (like shutter, empathy, reminna). I believe it is actually a Unity/Compiz problem rather than Network Manager specific. It definitely does not require a suspend/restore to happen, just enough time/activity.

What happens is after a period of use, usually less that a day, some kind of resource appear to run out or have leaked itself out. Then various things that require the resources stop works; so dynamically-created menus tend to be the first victims. The Network Manager VPN menu is definitely once of the most crippling because I know no work-around. Certainly no amount of restarting NM etc, will help. Logging out and logging back in again will fix it for a few hours, then you'll be screwed again.

I suspect, without any proof of knowledge, that the fault hits when you get close to needing to page or reclaim memory. I have 8GB and usually would be at ~7GB in used for applications/VM when it hits. That could just be coincidence though.

I have given up expecting any of major Unity bugs to get fixed, so I just live with it until I get my next laptop, which of course will definitely not have Unity. Maybe Mint, or hell, Windows XP would be a step up at this stage :-)

In the meantime, if anyone has any work-around that doesn't require a log-out I'd love to hear about it.

@Aaron, my workaround is to kill nm-applet (not Metwork Manager itself) and restart it. It does fix the issue for me... for a few hours, until it appears again (but that also applies to logging out and in).

It's annoying though because the only way I know of doing this is from a terminal, and then I am obliged to keep the terminal open forever (even though I relaunch nm-applet with "nm-applet &" with the "&"). But I guess someone can give us a solution for this?

Can confirm that this affects me as well (12.04 up to date as of today)

@matteosistisette I have been been launching nm-applet from the alt+F2 run dialog so that I don't have to keep a terminal open, give that a try.

It is still happening with 13.04. Workaround, from a terminal window:

killall nm-applet
nohup nm-applet &

Always works.

Could not associate with any other event, apparently it happens at random times.

Can also confirm this bug is still here in 13.04.

Has anyone observed this recently?