2009/4/7 Jose P.G <rayl...@gmail.com>: > Hi, i am logged as root and when i try to enable "Internet", "games"... and > i press "close" it doesn't works, it stays inactive.
*How* are you trying to edit the main menu in GNOME? Are you using alacarte ( /usr/local/bin/alacarte )? And just in case you are using alacarte and the following is your problem: In alacarte, under "Menus", if you click on "Applications" so that it's highlighted, the list of submenus shows up on the right hand side under "Items". The submenus listed there have tick boxes. If a submenu item shows up in italics there you can still click its box, but it will just untick itself again. That's because the submenus in italics are empty, and you cannot, AFAIK, make the menu show empty submenus. You make a submenu visible by populating it, e.g. by doing this: Make sure that "Applications" is expanded on the left hand side (under "Menus") and click on the submenu in question there, e.g. "Games". Now look if there are any games listed on the right hand side under "Items". If there are any installed and their boxes are not ticked, you should be able to tick their boxes, or otherwise you could install some, or manually configure any that are already on your system but not listed by clicking "New Item". This will magically make the "Games" submenu show up -- and now it will even stack ticked. (Seeing how alacarte thus sort of embodies everything that's wrong with pointy-clicky GUIs, configuring the same shite by editing a text file would probably be *much* easier, but I haven't yet gotten around to figuring out which file I'd have to edit there, mostly because of shitty documentation and a joke of a man page.) <OT-rant> Arguably this alacarte behaviour is a bug, but I so far couldn't be arsed to report it, largely because in my experience heavily Linux-centric projects rather predictably tend to have eager beavers who think that they're "doing important work" and "working hard" and "helping" by running around buffing and turfing perfectly good unresolved bug reports and closing them off as fast as they can without the bug ever getting addressed. It's not that they'd tell you to shut up and hack. They can mostly hack as little as I, which is rather poor. It's that the people who actually might be justified in telling you to shut up and hack don't even get to *see* your bug report, thanks to the eager beavers. The only chance to keep a bug open is to defend it and argue and talk and talk, and just generally waste much more energy than a humble report of a bug you yourself can't fix is worth. Nobody likes talking to a wall. Try adding an original and factual contribution to Wikipedia, and try reporting a new bug to, say, Ubuntu. Defend neither your Wikipedia edit nor your bug report. I dare you to see if the bug report will last as long as your Wikipedia edit. Don't let that stop you from reporting this bug though, but brace yourself. </OT-rant> But maybe the aforementioned behaviour isn't your problem at all -- in which case you'd have to give us more information about what you're experiencing. regards, --ropers
