GNU bug report logs - #76384
Incorrect mouse events / tool-bar event is undefined error.

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: mjk <mkajola <at> gmail.com>
Cc: luangruo <at> yahoo.com, 76384 <at> debbugs.gnu.org
Subject: bug#76384: Incorrect mouse events / tool-bar event is undefined error.
Date: Thu, 20 Feb 2025 09:30:27 +0200

> Date: Thu, 20 Feb 2025 03:49:28 +0200
> Cc: 76384 <at> debbugs.gnu.org
> From: mjk <mkajola <at> gmail.com>
> 
> Got some more info by testing. Rather interesting.
> The reason I mentioned the window manager, is because that I haven't had 
> much trust on gnome quality since version 3 (this is 46).
> 
> So I installed xcfe and tried there. Works fine. I do get mouse scroll 
> beeps on the tool bar, but I think that is kind of correct behavior. 
> Handlers just not defined.
> In this configuration mouse events in text window scroll only the text 
> window as expected.
> 
> On Xfce emacs (don't actually know where it comes from), pops up a 
> display that says that pure gtk version of emacs is not supported and 
> can cause crashes during transfers of large data, and recommends 
> installing emacs-gtk-x11 or emacs-lucid.
> To me this sounds like fedora related tweaking.
> 
> So I installed emacs-gtk-x11, and this seems to work fine, at least with 
> the simplest case with *scrach* buffer and no configuration of my own.
> 
> This seems to be some kind of mismatch between the pure gtk emacs and 
> gnome window manager, or maybe in the window manager itself. dunno.
> What is weird is that in the versions that work, I get the mouse event 
> errors from the tool-bar (as expected if they are not defined),
> but in non working config I get them from the working window area. But - 
> the tool bar works otherwise, so other mouse events are mapped correctly.
> So it is very surprising that different events are managed different 
> way. Seems that somebody is doing something fancy and overly complicated.
> 
> So, maybe this is not an emacs bug after all.

Thanks.  With which versions of Emacs did you try the above?  Po Lu
says Emacs 30 should probably solve this, so the versions you tried
could be relevant.

Another thing to try is Emacs 30 (currently available only as a
pretest) and see if the problem there exists even in your original
window manager.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.