Menu editor inconsistent behaviour

This behavior manifests as well on a clean install of 6.10. However, Mr. Noble notes a 75% failure rate. For me it is 100% - I've not been able to edit the GNOME menu in any way. This includes checking and unchecked entry to make it visible.

Thank you for your bug. What menu editor do you use, alacarte? If you close the menu editor and restart it are the changes still applied? If you restart the gnome-panel do you get them applied?

I can confirm problem 2 listed above, using alacarte in Dapper.

I created a menu entry in a submenu. I used the icon button to
bring up the Icon Selector window, browsed for the directory that
I wanted, selected the icon, and clicked on OK in the Icon Selector
window. The icon showed up in the Entry Editor window, but *not*
in the Alacarte Menu Editor window, and it still did not appear
after closing the Entry Editor window. I edited the entry again,
selected the icon again, and then selected Run In Terminal. This
caused the icon to appear back in the Alacarte Menu Editor. So I
clicked again on Run In Terminal (since I don't actually want that
option), and closed the Entry Editor. Now the menu has the icon
that I selected.

I have had other problems with the Name not being updated after
changing it in Entry Editor, but at the time I didn't try the
"click on Run In Terminal twice" trick.

I can confirm #1 and #2 in a clean install of the release version of Feisty.

As for #1, I tried to create a new menu called "Wine", but it just went into disabled mode. Enabling it has no effect.

As for #2, I've noticed this when trying to enable the "Other" menu and it stays disabled. Same goes for "Education" and "Debian". Neither changes from italic text to show they're enabled.

I'll add one too:

5. Menu items gets duplicated in the Main Menu editor before your eyes. Enabling Konqueror in the System Tools menu creates three additional menu items which are disabled. System->Preferences->Control Center also has one (disabled) shadow item.

All of this was detected using the new "Main Menu" button in the Control Center.

If I may suggest something to look for - an uninitialized toggle variable seems to be a good candidate. :)

Screen shots to show the behavior in the #1, #2 and #5 (above).

http://img161.imageshack.us/img161/9902/snapshot3gs2.png

http://img161.imageshack.us/img161/3782/snapshot4li9.png

This is failing on both edgy and feisty for me...

On Feisty, at least one of these problems still exist. When you drag one item from one section to another, the GUI looks like it is going to move the item. The item is removed from the from-section but never appears in the to-section. When you go back to the from-section, the item is still there. The result is that you have to create a new item in the to-section, copy all fields and the icon from the old item and delete it. It's abit annoying.

Could somebody makes a short description of what happens under feisty if the bug is still happening?

Go to System -> Preferences -> Main Menu and open the editor. Select any section and try to enable a disabled option by checking the box. It highlights the section with a different background color but does not insert a check in the box. Essentially, will not toggle the options on/off and will not change the menu options after closing the applet.

As I said above, this bug is in Feisty. In fact it's worse in Feisty than in Dapper. In Dapper I could enable the "Other" menu and create a "Wine" menu, but not in Feisty. The duplicate entries are more or less consistent from Dapper to Feisty though.

Additional info: In Feisty, the "Other" menu is visible when I install a program which is destined to install an icon there, for instance Celestia, gdeb or Gnome Predict. But it stays disabled if it's empty.

marking unconfirmed, the bug is not clear. Likely an upstream issue, somebody getting the bug should open it on bugzilla.gnome.org with a clear description

Same here, neither the menu or menu editor show changes until the computer is restarted. Also, this doesn't happen every time. . . on some days it works on others it doesn't.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Closing this report for now, please feel free to re open it if you experience the same issue in a Gutsy Gibbon installation. Thanks in advance.