-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Steam detects wrong primary monitor #11130
Comments
Should vertical monitors be ignored by Steam if there are more than 1 monitors, would this be a possible solution? |
I would say, no. It should honor the "primary" monitor setting of your desktop compositor. OR let you choose in steam own settings primary monitor to launch games in. (then again, for me it has always worked in Plasma + Wayland. Had previously issues in XFCE + X11) |
I worked around this issue by running Maybe this is a KDE bug and it should be setting the X primary monitor even when KDE is running in wayland mode? Not sure whose responsibility this is. |
I wish X/Wayland/KDE/other WMs had a concept of not only "primary monitor" but also "entertainment monitor", for video and gaming. |
This also happens on Fedora 41 KDE, running Plasma 6.2.2 fix by @evanc577 works but I have to run it every time before starting steam |
Your system information
Please describe your issue in as much detail as possible:
In a triple monitor setup, Steam detects the leftmost monitor as the primary display and opens all content (start splash, fullscreen games, big picture mode, etc.) on that monitor, instead of the actual primary display set in KDE Plasma settings. I only started experiencing this issue recently, after returning from a 3 week vacation, but it was working correctly in June.
Plasma monitor configuration, center screen is set as highest priority:
(expand) Steam system information, note that the display detected is the leftmost 1080p 24 inch vertical display, rather than the other two 4k 144hz horizontal displays.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: