Comment 30 for bug 415101

OK, more data to add to the confusion.

* With emacs23-gtk, set up a mode that has a custom menu (e.g. shell script, HTML Helper). Then start the calendar (M-x calendar). Starting in the non-calendar window, watch what happens to the custom menus. On system A:

** The edit menu does not work.

** The custom menu doesn't work at all. Now toggle between the two (C-x o).

** None of the custom menus work. Toggle back (C-x o again).

** None of the custom menus work.

* On system B, as above:

** The Edit menu works.

** The custom menu works. Now toggle between the two (C-x o).

** None of the custom menus work, except the Scroll menu. Except that produces what should be the shell script mode menu (!). Note that the Edit menu is removed (This is normal; Emacs 22.2.1 on Jaunty does the same). Toggle back (C-x o again).

** The custom menu works. The edit menu fails to work.

System A is a Lenovo r51 laptop with a radeon video gpu (http://www.charlescurley.com/Lenovo.R51.html).

System B is a Fit-PC 1 (http://www.fit-pc.com/fit-pc1/fit-pc-1-0-specifications.html).

Clearly the different video cards make the drivers suspect here.

It also occurs to me that calendar mode and its menus have been around a lot longer than shell-script mode's menu (22.2.1 has a different custom menu). So are there two different ways to initialize a custom menu, one of which isn't working correctly in the gtk version?

Of the two suspicions, I am inclined toward the second. I can't see emacs reaching down far enough such that the driver code would make a difference.