On Sat, 19 Apr 2025 18:31:28 +0200 Axel Rohde <dr.a.ro...@gmx.de> wrote: > The bug is actually already present in FVWM2 since 2.6.8, there I've been > doing the following to work around the issue: > git revert ffe942d66cdb1a24d761d9e89c1a4dab49f2400c >
Have you tested is reverting that commit in fvwm3 has any effect on this issue? jaimos
