Bug 459190

Summary: Selecting the output monitor does not work for XWayland games with the "Apply Scaling Themselves" setting enabled
Product: [Plasma] kwin Reporter: indecisiveautomator
Component: wayland-genericAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: wishlist CC: kde, nate, postix, xaver.hugl
Priority: NOR Keywords: regression
Version First Reported In: 5.25.90   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description indecisiveautomator 2022-09-15 22:07:49 UTC
SUMMARY
Many games give you the option to choose which display the game should output on, typically exclusively for fullscreen. This is... touchy at best for games, including on Windows and macOS, but games that I own which I previously was able to use this option correctly with in Plasma 5.25 do not work with the 5.26 Beta.

Yakuza 0 is the game I tested with. It will allow me to change and apply the setting say from Display 3 to Display 2 , but it won't actually change displays like it does on I believe 5.25. Going back out and into the game's settings again shows the setting back to Display 3.

Of course there are various other situations where this could happen, games just display this more clearly.


STEPS TO REPRODUCE
1. Open an application that allows you to change the fullscreen output display such as a game.
2. Attempt to change the output display
3. Nothing happens.

OBSERVED RESULT
X11 Games (and likely other applications with similar functionality) do not change output displays when their option is selected. 


EXPECTED RESULT
X11 Games should change their output display when the option is selected, if it worked previously for that game/application in 5.25.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.19.8-zen1-1-zen (64bit)
KDE Plasma Version: 5.25.90
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6

ADDITIONAL INFORMATION
Games can still be changed by using the Window menu and changing the output display.

This problem is very, very minor and seems to be a small feature regression which needs to be fixed upstream rather than on the Plasma side. Thought I'd report it here to be safe though as I'm currently testing the 5.26 beta :-)
Comment 1 Zamundaaa 2022-09-24 23:01:23 UTC
Can you attach the output of "kscreen-doctor -o" and xrandr? There could be a difference between where Xwayland (and thus the game) assumes the outputs are and where KWin actually has them, which might cause such issues
Comment 2 Zamundaaa 2023-01-23 14:36:26 UTC
.
Comment 3 Bug Janitor Service 2023-02-07 03:54:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2023-02-22 03:45:51 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!