> > > > then I see the extra LeaveNotify / EnterNotify / KeymapNotify sequence
> > > > in xev
>
> Forget about these; that's just how X works.
I dusted off old memories about the patches that I'm carrying in my
home fvwm binary and not my work one, and I think that this has come
up before and had a patch proposed before. If I'm right, see this
fvwm-workers discussion from early September 2014:
https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03528.html
This change was reverted here:
https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03596.html
apparently because of this issue:
https://www.mail-archive.com/fvwm-workers@fvwm.org/msg03593.html
This came out of my May 2013 report of a very similar issue with
Darktable, which is also a GTK+ application. At the time I wound up
localizing it to those same Mouse 1 'A' bindings I have (in email between
me and Thomas Adam, not captured in the mailing list archives). The
initial fvwm thread about it is here:
http://www.mail-archive.com/fvwm@fvwm.org/msg02464.html
This is apparently also a Debian bug report with somewhat more
specific details about the GTK+ bits with problems, from 2011:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642151
I've built a version of git tip fvwm with the patch from Thomas
Adam and it appears to fix this issue for me (although presumably
the patch still has the issue that caused it to be reverted).
- cks
