Describe the bug
When using a dual-monitor set up on Linux, entering fullscreen put the content on the screen selected on the drivers settings window, but the second screen is also blanked. Ares correctly detects the monitors, but changing the fullscreen target monitor still blanks whichever screen is not the target. This is happening in all of the following scenarios:
Linux Mint using X, Nvidia video card, all versions from 134 through 137, plus the latest github master as of today (April 26).
Fedora, using Wayland, Intel video, version 137, and today's github master.
On both systems, I tested all available Ares drivers (OpenGL 3 and 2, xshm, and whatever else I can't remember right now).
This is even happening without a rom loaded.
To Reproduce
Steps to reproduce the behavior:
Build any Ares version from v134+, in one of the scenarios above, using two 1080 screens.
Assign a fullscreen hotkey.
Press the fullscreen hotkey. If you don't have a rom loaded, both the screens will go black. If you have a rom loaded, the rom will appear on whichever screen is assigned in the settings, and the other screen will be black.
Expected behavior
Entering fullscreen should only affect either the assigned target monitor.
Screenshots
(I admit, not a great screenshot, but the right side is supposed to be my desktop.)
Additional context
Here's a video showing the issue in action. (I'd already assigned a fullscreen hotkey): https://youtu.be/SwCscJweqZE
Describe the bug When using a dual-monitor set up on Linux, entering fullscreen put the content on the screen selected on the drivers settings window, but the second screen is also blanked. Ares correctly detects the monitors, but changing the fullscreen target monitor still blanks whichever screen is not the target. This is happening in all of the following scenarios:
To Reproduce Steps to reproduce the behavior:
Expected behavior Entering fullscreen should only affect either the assigned target monitor.
Screenshots (I admit, not a great screenshot, but the right side is supposed to be my desktop.)
Additional context Here's a video showing the issue in action. (I'd already assigned a fullscreen hotkey): https://youtu.be/SwCscJweqZE