After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 593202 - emacs22-gtk generated menus are blank (GTK only)
emacs22-gtk generated menus are blank (GTK only)
Status: RESOLVED DUPLICATE of bug 593249
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
csw
Depends on:
Blocks:
 
 
Reported: 2009-08-26 18:23 UTC by Bernhard Koenig
Modified: 2009-09-01 09:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot of the missing Emacs menu (34.99 KB, image/png)
2009-08-26 18:24 UTC, Bernhard Koenig 		Details

Description Bernhard Koenig 2009-08-26 18:23:24 UTC 
The attached picture should say it all.
I have tested C/C++, Python, Erlang and they all show up blank.
I've had this problem for a while not (a month or so, maybe?), but I'm not sure exactly when it showed up. I suspected it was just me for a while, but I've tested with blank ~/.emacs.d directory for defaults as well.

This is an emacs problem in Ubuntu and it is currently reported as https://bugs.launchpad.net/ubuntu/+source/emacs22/+bug/415101

We were wondering if it has to do with the new gtk version of 2.28, since this happened during the switch from Jaunty to Karmic. Please feel free to reject the bug, if you think it is not gtk related, we only have these problems in the gtk-emacs though.
Comment 1 Bernhard Koenig 2009-08-26 18:24:48 UTC 
Created attachment 141774 [details]
Screenshot of the missing Emacs menu
Comment 2 Alexander Larsson 2009-09-01 09:30:25 UTC 
Its kind of difficult to say this is a "gtk+" bug, as emacs gtk+ integration does some pretty weird stuff mixing gtk+ and direct X accesses. However, i have left bug 593249 open to track this. I added some comments there on how emacs could best solve this, but I've not actually talked to upstream about this, which it would be nice if someone did.

*** This bug has been marked as a duplicate of bug 593249 ***