I believe I came across this myself. Running
wine <app> directly under
xpra start appears to be totally functional, and responds to mouse input; however no keypress events are acknowledged by the wine application.
I tried instead launching the
wine process by hand under an
xterm instance via
xpra start --start-child=xterm , and found that the keystrokes intended for the
wine application in fact reflect in the xterm window. From this behavior, I assumed the issue was focus based.
I found that by running under
start-desktop with a window manager, the process then begins to behave as expected; eg
xpra start-desktop --start=blackbox --start-child=wine winecfg
Hopefully this provides some assistance in tracking down the root cause of this behavior, or at very least, a viable workaround for others.
PS. Nice to see a Trac instance still going strong! \m/
Workaround for wine apps in r26291: start the server with:
xpra start --env=XPRA_FORCE_XSETINPUTFOCUS=1 ...
Maybe we can change the default to always call XSetInputFocus rather than checking the "input_field"? (or maybe it isn't set properly for wine apps?)
r26312 changes the default to always call
XSetInputFocus for 4.1
If this causes problems, we can revert it.
this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/2698