https://bugs.winehq.org/show_bug.cgi?id=50449
--- Comment #2 from g0re g0re@null.net --- (In reply to Rémi Bernon from comment #1)
I've tried reproducing this but to no avail. Could you provide more detail, like:
- Does it happen as soon as you press a key and move your mouse, or if it
happens after a while? 2) Is it a MinGW build? 3) Does it require some specific hardware (gaming mouse with high polling rate)?
Also as you seem to be able to reproduce the bug with various wine versions, maybe run git bisect to track down the exact regressing commit? See https://wiki.winehq.org/Regression_Testing
1- it happens soon the keyboard and mouse are used at the same time.
2- no idea what build system Zdaemon's devs uses ( it is closed source )
3- tested with 2 mouses, see bellow
-----------------------------------------------------------------
I think that I've discovered the real culprit.
I renamed ~/.wine to create a new one and the problem goes away.
So, I compared via winecfg what the difference.
Discovered that I have d3d9.dll and d3dcompiler_47.dll set to native/builtin.
These 2 files are used by ReShade ( https://reshade.me ) but I don't use it anymore.
Some change on wine 5.15 behavior affects the ReShade's d3d9.dll and affects user input behavior.
Before that, I tested 2 USB mouses. A 800dpi and a 1000dpi with no solution.
However, I will try to find via git bisect which commit is the problem.
For curiosit, you can look at https://old.reddit.com/r/linux_gaming/comments/b2hi3g/reshade_working_in_win... how ReShade is used
OBS: changes on wine 5.15 affects GShade ( https://gposers.com/gshade/ )