Comment 5 for bug 1242937

> this would require a distro patch on GTK+ to support

I assume that's undesirable for some reason.

> we could instead try to blacklist freeciv from having global menus
> entirely (the same effect as specifying UBUNTU_MENUPROXY=
> on the command line).

Well, that would clearly solve the problem.

In your patch, you catch names "freeciv" and "freeciv-gtk2". Is the former necessary?
Also, I suggest you include "freeciv-gtk3" -- this is a new client in 2.4.x, using the Gtk3 toolkit, but it uses menubars in the same way so I expect it would suffer the same issue (although I haven't tested it).

> The downside is that the main application menu bar will not
> appear in the global menu....

Indeed.
I assume this is fairly hard to revert? -- that is, if some future change in Freeciv somehow renders it compatible with globalmenu, there's no way for users or Freeciv itself to override the blacklisting? (And if you remove it from unity-gtk-module, then users of older versions of Freeciv will once again see breakage. So it's hard to coordinate outside of the Ubuntu-packaged Freeciv version.)