http://bugs.winehq.org/show_bug.cgi?id=32602
Bug #: 32602 Summary: keyboard/mouse focus intermittent failure on fvwm2: problem tracked to failure of WINE to obey WM_HINTS ICCCM guidelines Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: lkcl@lkcl.net Classification: Unclassified
there's a long-standing highly intermittent and difficult to reproduce bug in wine which has been repeatedly "blamed" onto fvwm2, the solution for which may turn out to be the solution to bugs #30583, #29010, #19874 and so on.
after several years of tolerating the bug, reporting the bug, having it closed by wine developers and being told, "it's a bug in fvwm2", and finally asking the fvwm2 what the problem was, a well-known "solution / workaround" was suggested, tried, and confirmed as immediately "fixing" the problem.
however, the workaround is well-known by the fvwm2 developers as being necessary to tolerate broken programs (including wine) that do not properly follow ICCCM guidelines.
the following advice, laid out in the fvwm man page, and kindly provided by the fvwm2 developers, should give enough information for the wine developers to track down the problem.
-----
If Lenience fixes the problem, the window is not indicating that it accepts input.
Here's the section of the Fvwm man page:
The ICCCM states that windows possessing the property
WM_HINTS(WM_HINTS): Client accepts input or input focus: False
should not be given the keyboard input focus by the window manager. These windows can take the input focus by themselves, however. A number of applications set this property, and yet expect the window manager to give them the keyboard focus anyway, so fvwm provides a window style, Lenience, which allows fvwm to overlook this ICCCM rule. Even with this window style it is not guaranteed that the application accepts focus.