Alex, yes, I've installed all *.deb from build-area.
I'm attaching a python spam script that I modified from the examples network-manager comes with that can reproduce the issue for me in ~1 minute by repeatedly adding and deleting a connection via dbus. I see the bug appear after about 500 iterations, but I have > 50 wifi networks visible in my menu at the moment, so it might take others many more iterations if we think that's relevant. During running the script, if you open the nm-applet menu, you should see it flickering madly. (Sometimes the script will stall for a few seconds due to a dbus timeout--haven't debugged this yet, gah...)
I can't reproduce it using this spam script running under valgrind though, probably due to valgrind's performance penalty (the menu doesn't visibly flicker when I run the script). I'll try to get a valgrind log the more natural way by just letting it run, which hopefully will still take ~24-48 hours, assuming I don't have to reboot for anything in the meantime.
Alex, yes, I've installed all *.deb from build-area.
I'm attaching a python spam script that I modified from the examples network-manager comes with that can reproduce the issue for me in ~1 minute by repeatedly adding and deleting a connection via dbus. I see the bug appear after about 500 iterations, but I have > 50 wifi networks visible in my menu at the moment, so it might take others many more iterations if we think that's relevant. During running the script, if you open the nm-applet menu, you should see it flickering madly. (Sometimes the script will stall for a few seconds due to a dbus timeout--haven't debugged this yet, gah...)
I can't reproduce it using this spam script running under valgrind though, probably due to valgrind's performance penalty (the menu doesn't visibly flicker when I run the script). I'll try to get a valgrind log the more natural way by just letting it run, which hopefully will still take ~24-48 hours, assuming I don't have to reboot for anything in the meantime.