Should Emacs set UBUNTU_MENUPROXY=0 unconditionally?

[Philipp Stephani <p.stephani2@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]

Hi,

etc/PROBLEMS has (
http://git.savannah.gnu.org/cgit/emacs.git/tree/etc/PROBLEMS?h=emacs-25.1-rc1#n1360
):

*** Warning messages when running in Ubuntu

When you start Emacs you may see something like this:

(emacs:2286): LIBDBUSMENU-GTK-CRITICAL **: watch_submenu: assertion
'GTK_IS_MENU_SHELL(menu)' failed

This happens if the Emacs binary has been renamed.  The cause is the Ubuntu
appmenu concept.  It tries to track Emacs menus and show them in the top
panel, instead of in each Emacs window.  This is not properly implemented,
so it fails for Emacs.  The order of menus is wrong, and things like
copy/paste
that depend on what state Emacs is in are usually wrong (i.e. paste disabled
even if you should be able to paste, and similar).

You can get back menus on each frame by starting emacs like this:
% env UBUNTU_MENUPROXY= emacs


Are there any downsides of setting UBUNTU_MENUPROXY? It seems that it can
only ever fix problems, at least until the integration into the Unity menu
is fixed. If that is the case, should Emacs set the variable
unconditionally on startup (for its own process, not for subprocesses)?

Thanks,
Phil

[-- Attachment #2: Type: text/html, Size: 1568 bytes --]