-
Notifications
You must be signed in to change notification settings - Fork 69
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
Ubuntu two monitor setup and fullscreen modus: Game always starts on secondary monitor #2542
Comments
Hello @ptck, this issue is already being tracked at #60 with a possible workaround at #60 (comment). Also, your side note is being tracked at #665. Closing as a duplicate. |
@kisak-valve Thanks for #60. Unfortunately none of the suggestions there helped. |
Just to check, did you remove the |
I've gone ahead and transferred this issue report to #60 (comment). Let's continue the discussion there. |
Yes I did. |
Your system information
Steam
->Help
->System Information
) in a gist: https://gist.github.com/ptck/1b0f4e62177d60ab26241e19539da60dPlease describe your issue in as much detail as possible:
I have two monitors. One with 1920x1080 resolution (primary) and an old 4:3 monitor (secondary) on the left side on my desk.
I had this problem under Ubuntu 16.04 and also now on 20.04 (I set my computer completely new up for this). When I start the game it always starts on my 4:3 monitor. Dragging it over to the primary screen doesn't help as when I hover over a button with my mouse the game register it as a hover somewhere else. Probably because the game is still in the 4:3 modus. Adding "-fullscreen" to launch options doesn't help. The only solution is to disconnect my 4:3 monitor from my PC so that I have only one monitor.
Also as a side note: If I start the game I get for a couple for seconds a black screen and a "csgo_linux64 not responding" warning before the CS:GO starting screen appears. All in all the game needs 15-20 seconds to start up.
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: