LXDE Forums

It is a minor annoyance, one that is easily overlooked, so probably has not been discussed before: When I click the main menu button (apps./prefs/etc) and browse, usually she will not collapse when I move my cursor to an application or to do other things. I normally just click run, then cancel to close the menu.

The "workaround" to close the thing is minor enough for me and other techies to overlook. However, for wife, retired parents, and kids, this is too confusing, and they go ballistic! This needs to be fixed, asap.

I think the short term work around is create a launcher below logout called "Close Start Menu" with command "null". But this is lame.

I don't see threads. Probably, only because a techie knows, "The gui is expecting me to choose 'something...anything', because the programmers forgot the alternative of not choosing anything.

Clicking anywhere on the open desktop should close the menu.

+1. That's pretty simple.

This only works for a while, then LXDE goes flakey and keeps the Start Menu open!! Clicking anywhere doesn't work. You can even minimize all windows and click on the wall paper and the menu WILL NOT collapse.

So, this is a bug, not just a missing design. The bug will crop up at random times. (Kinda like bug where the panel goes randomly crashing when editing /adding items. Fortunately, the panel self-revives after it crashes in under a second, unlike the gnome menu.)

The Start menu is obviously waiting for something after it is opened... anything to be clicked, but only in the menu, or it will not close. The only work around is to click something and cancel, or to make a dummy launcher and put with main categories.

Have you tried re-installing lxpanel? What distro are you using?

I was doing it frequently. Now, rarely, but still.

Pinguy 12.04, based on Ubuntu 12.04. I am using a desktop rotator script. I wonder if when it rotates while I am browsing the Start menu items, it may cause some part of the code to miss the directive to close the menu. The directive was sent, just not heard, so clicking anywhere will not resend the directive.

I hypothesize this as my wall paper was rotating too often when it was first happening alot, because of the early stage of the wallpaper rotator script.