🚀 go-pugleaf

 > Path: fbi-news!grossjoh
 > From: grossjoh@linus.informatik.uni-dortmund.de (Kai Grossjohann)
 > Newsgroups: gnu.emacs.bug
 > Followup-To: gnu.emacs.help
 > Date: 31 Aug 1994 15:39:39 GMT
 > Organization: Universitaet Dortmund, Lehrstuhl Informatik VI
 > Lines: 15
 > Distribution: gnu
 > References: <9408310039.AA28162@igor.Rational.COM>
 > Reply-To: Kai Grossjohann <grossjoh@sally.informatik.uni-dortmund.de>
 > Nntp-Posting-Host: linus.informatik.uni-dortmund.de
 > 
 > >>>>> "Gary" == Gary Barnes <geb@rational.com> writes:
 > 
 >   Gary> When a menubar menu is popped up, it goes at coordinate 0,0
 >   Gary> for the frame.  It is supposed to go next-to and just-under
 >   Gary> the menubar button.  At 0,0 they come up over/on-top-of the
 >   Gary> menu bar; hiding it from sight.  Also, when this happens, the
 >   Gary> selected menu items don't track the mouse very well, they are
 >   Gary> offset by a dozen or so pixels.  Also, submenus come up where
 >   Gary> they would come up if the main menu had come up in the right
 >   Gary> place.
 > 
 > I heard that this happens when you have Emacs*geometry in your X
 > resource database.  You should instead put Emacs.geometry in there.

Or do *nothing* but wait for Emacs-19.26 (to be released soon).