https://bugs.winehq.org/show_bug.cgi?id=56789
--- Comment #6 from jubilantjerry@gmail.com --- @Rafał Mużyło
I apologize, I didn't have any good evidence connecting XInput to OpenGL. It was the only pair of features that had results when I searched them together on Google, so my assumption was that they were related.
The errors from comment 2 no longer happen on version 9.11. Originally, they only happened after applications have already crashed due to the suspend event (with error XI_BadDevice). Probably, the Wine server was already in an unstable state after having some applications crashing, causing more crashes that are victims of something else. I agree we can ignore the BadWindow family of problems.
However, the fact remains that I observe all applications crashing on Wine versions 9.4 and above, after the computer suspends. This applies even for built-in applications like winecfg and regedit.
Suspend refers to sleep action caused by the the "pm-suspend" command, which is also the same event that happens when the laptop's lid is closed, when the "Suspend" option from the power menu is chosen, or when the laptop is left idle for a long time. This causes suspend-to-RAM based on what I see in /sys/power/mem_sleep.
I'm not sure if this is related to DPMS. If I understand correctly, there is the suspicion that the bug occurs when the monitor is turned off. However, if I use any of the commands "xset dpms force [off|standby|suspend]", Wine applications do not crash. Only a suspend-to-RAM causes the crash.
I'm not familiar enough with Wine to know what other logs or information to provide, could you suggest additional information beyond the version number, machine details, and Wine logs just prior to the crash event? Thanks.
I use a Dell Inspiron 7577 laptop and did not modify the hardware. Is there information in the logs that point to a hardware problem?