https://bugs.winehq.org/show_bug.cgi?id=57547
Rémi Bernon rbernon@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon@codeweavers.com
--- Comment #22 from Rémi Bernon rbernon@codeweavers.com --- The issue is likely that Wine got access to mouse and keyboard devices, through hidraw or evdev. This is possibly the case if you have added your user to the input group, because you run wine as root, or because of some unrestricted udev rules.
We don't support mouse and keyboard devices in winebus and in the HID stack at the moment, and they are known to crash somewhere in the stack.
You should also probably not give access of such devices directly to user-space applications, and only game controller are usually considered safe to access (and they are openly accessible through evdev, to the contrary to the mouse and keyboard evdev devices which are usually exclusively opened by the display server on startup).