You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I open some games with wine that have launchers, for example Overwatch 2 (battle net), League of Legends installer, guild wars 2 launcher, xmonad becomes unresponsive, window borders start flickering, cpu goes to 100% usage and the wm stops functioning until I close the game. It shouldn't do that.
Steps to Reproduce
Run with wine any of the aforementioned installers/launchers, making sure you have Hacks.windowedFullscreenFixEventHook and/or fullscreenSupport.
Configuration File
Please include the smallest full configuration file that reproduces
the problem you are experiencing:
With xmonad-contrib commit 673de11ca876a4a58cae3a4d52e36260f66aa6cc
edit1: I've edited because of a mistake on my part, I had tried in a vm with default config and it had crashed, so I thought it crashed because of that... either way, now I tried on my real hardware and narrowed the issue down even more. for some reason, when it launches, xmobar starts using a lot of cpu, but that should be another issue.
Problem Description
When I open some games with wine that have launchers, for example Overwatch 2 (battle net), League of Legends installer, guild wars 2 launcher, xmonad becomes unresponsive, window borders start flickering, cpu goes to 100% usage and the wm stops functioning until I close the game. It shouldn't do that.
Steps to Reproduce
Run with wine any of the aforementioned installers/launchers, making sure you have Hacks.windowedFullscreenFixEventHook and/or fullscreenSupport.
Configuration File
Please include the smallest full configuration file that reproduces
the problem you are experiencing:
Checklist
I've read CONTRIBUTING.md
I tested my configuration
xmonad
version 0.17.1 (arch repos version)xmonad
commit 5ecdf75xmonad
commit eeac754xmonad-contrib
commit 673de11ca876a4a58cae3a4d52e36260f66aa6ccedit1: I've edited because of a mistake on my part, I had tried in a vm with default config and it had crashed, so I thought it crashed because of that... either way, now I tried on my real hardware and narrowed the issue down even more. for some reason, when it launches, xmobar starts using a lot of cpu, but that should be another issue.
edit2: Attached video demonstrating it: https://youtu.be/Qz2Mbpab0p8
The text was updated successfully, but these errors were encountered: