Steam Games Launch On Wrong Monitor

Issues & Assistance Unsupported Software (AUR & Other)
1

Normally, I’m able to find a solution via research for my problems, but none of the threads I’ve come across have resolved my issues. Every game I launch, launches in my left monitor instead of my center. I’ve tried setting xandr via terminal, with no change, tried logically moving my monitor to the right with no change. I can move the app to my main monitor with hotkeys, however, since my far left monitor is 1080p and my other 2 are 1440p, a lot of games I can not set to the proper resolution with this method. If I disable the monitor I can get it to work, but that’s a pretty annoying workaround. Is there an actual fix for this?

I have Garuda Dragonized with KDE Plasma, latest patches applied, proprietary NVidia drivers installed through official repository.

I truthfully can’t find much short of the xandr command.

Thanks!

System:
Kernel: 6.16.8-zen3-1-zen arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=d7ae3ecb-bb98-468d-a4f6-02809d595c4d rw rootflags=subvol=@
quiet loglevel=3
Desktop: KDE Plasma v: 6.4.5 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Gigabyte model: X870 GAMING WIFI6 serial: N/A
uuid: 03ff0200-0400-0580-ee06-000700080009 UEFI: American Megatrends LLC.
v: F6a date: 05/05/2025
CPU:
Info: model: AMD Ryzen 9 9950X3D socket: AM5 bits: 64 type: MT MCP
arch: Zen 5 gen: 5 level: v4 note: check built: 2024+ process: TSMC n4 (4nm)
family: 0x1A (26) model-id: 0x44 (68) stepping: 0 microcode: 0xB404023
Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 16 threads: 32 tpc: 2
smt: enabled cache: L1: 1.2 MiB desc: d-16x48 KiB; i-16x32 KiB L2: 16 MiB
desc: 16x1024 KiB L3: 128 MiB desc: 1x32 MiB, 1x96 MiB
Speed (MHz): avg: 2982 min/max: 624/5756 boost: enabled
base/boost: 4300/5750 scaling: driver: amd-pstate-epp governor: powersave
volts: 1.3 V ext-clock: 100 MHz cores: 1: 2982 2: 2982 3: 2982 4: 2982
5: 2982 6: 2982 7: 2982 8: 2982 9: 2982 10: 2982 11: 2982 12: 2982
13: 2982 14: 2982 15: 2982 16: 2982 17: 2982 18: 2982 19: 2982 20: 2982
21: 2982 22: 2982 23: 2982 24: 2982 25: 2982 26: 2982 27: 2982 28: 2982
29: 2982 30: 2982 31: 2982 32: 2982 bogomips: 274709
Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a
ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA GB203 [GeForce RTX 5080] vendor: ZOTAC driver: nvidia
v: 580.82.09 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
status: current (as of 2025-08) arch: Lovelace code: AD1xx
process: TSMC n4 (5nm) built: 2022+ pcie: gen: 5 speed: 32 GT/s lanes: 16
ports: active: DP-1,DP-2,DP-3 empty: HDMI-A-1 bus-ID: 01:00.0
chip-ID: 10de:2c02 class-ID: 0300
Display: unspecified server: X.Org v: 24.1.8 with: Xwayland v: 24.1.8
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nv_platform,nvidia,nvidia-nvswitch
display-ID: :1 screens: 1
Screen-1: 0 s-res: 7040x1649 s-dpi: 96 s-size: 1862x436mm (73.31x17.17")
s-diag: 1912mm (75.29")
Monitor-1: DP-1 pos: bottom-r model: HP OMEN 27i IPS serial: <filter>
built: 2020 res: mode: 2560x1440 hz: 165 scale: 100% (1) dpi: 109 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
Monitor-2: DP-2 pos: bottom-l model: Dell S2721HGF serial: <filter>
built: 2020 res: mode: 1920x1080 hz: 144 scale: 100% (1) dpi: 82 gamma: 1.2
size: 597x336mm (23.5x13.23") diag: 685mm (27") ratio: 16:9 modes:
max: 1920x1080 min: 640x480
Monitor-3: DP-3 pos: primary,top-center model: C32C1S serial: <filter>
built: 2023 res: mode: 2560x1440 hz: 240 scale: 100% (1) dpi: 93 gamma: 1.2
size: 697x392mm (27.44x15.43") diag: 800mm (31.5") ratio: 16:9 modes:
max: 2560x1440 min: 640x480
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
inactive: wayland,device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.82.09
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 5080/PCIe/SSE2
memory: 15.55 GiB
API: Vulkan v: 1.4.321 layers: 11 device: 0 type: discrete-gpu
name: NVIDIA GeForce RTX 5080 driver: nvidia v: 580.82.09
device-ID: 10de:2c02 surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 20.1.8 256 bits) driver: mesa llvmpipe v: 25.2.3-arch1.2 (LLVM
20.1.8) device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: corectrl, lact, nvidia-settings,
nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: NVIDIA driver: snd_hda_intel v: kernel pcie: gen: 5 speed: 32 GT/s
lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:22e9 class-ID: 0403
Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
lanes: 16 bus-ID: 74:00.6 chip-ID: 1022:15e3 class-ID: 0403
Device-3: SteelSeries ApS Arctis Nova Pro Wireless
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-3:3 chip-ID: 1038:12e0 class-ID: 0300
API: ALSA v: k6.16.8-zen3-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.4.8 status: n/a (root, process) with:
1: pipewire-pulse status: active 2: wireplumber status: active
3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel 82599 10 Gigabit Network vendor: Beijing Sinead
driver: ixgbe v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 link-max:
lanes: 8 port: e000 bus-ID: 05:00.0 chip-ID: 8086:1557 class-ID: 0200
IF: enp5s0 state: up speed: 10000 Mbps duplex: full mac: <filter>
Device-2: Realtek RTL8851BE PCIe 802.11ax Wireless Network
driver: rtw89_8851be v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
port: d000 bus-ID: 07:00.0 chip-ID: 10ec:b851 class-ID: 0280
IF: wlp7s0 state: down mac: <filter>
Device-3: ASUSTek ROG STRIX SCOPE II 96 WIRELESS
driver: hid-generic,usbhid type: USB rev: 2.0 speed: 12 Mb/s lanes: 1
mode: 1.1 bus-ID: 9-1.3:3 chip-ID: 0b05:1aae class-ID: 0300
serial: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: Realtek Bluetooth Radio driver: btusb v: 0.8 type: USB rev: 1.0
speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:5 chip-ID: 0bda:b850
class-ID: e001 serial: <filter>
Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.3
lmp-v: 12 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 3.68 TiB used: 1.23 TiB (33.4%)
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW020T8
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 34.9 C scheme: GPT
SMART: yes health: PASSED on: 5y 123d 6h cycles: 447
read-units: 397,480,325 [203 TB] written-units: 435,357,508 [222 TB]
ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Samsung model: SSD 990 PRO with
Heatsink 2TB size: 1.82 TiB block-size: physical: 512 B logical: 512 B
speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7
temp: 38.9 C scheme: GPT
SMART: yes health: PASSED on: 174d 15h cycles: 161
read-units: 31,790,828 [16.2 TB] written-units: 54,023,306 [27.6 TB]
Partition:
ID-1: / raw-size: 806.45 GiB size: 806.45 GiB (100.00%)
used: 516.82 GiB (64.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p6
maj-min: 259:7
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
used: 31.4 MiB (32.7%) fs: vfat block-size: 512 B dev: /dev/nvme1n1p1
maj-min: 259:2
ID-3: /home raw-size: 806.45 GiB size: 806.45 GiB (100.00%)
used: 516.82 GiB (64.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p6
maj-min: 259:7
ID-4: /var/log raw-size: 806.45 GiB size: 806.45 GiB (100.00%)
used: 516.82 GiB (64.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p6
maj-min: 259:7
ID-5: /var/tmp raw-size: 806.45 GiB size: 806.45 GiB (100.00%)
used: 516.82 GiB (64.1%) fs: btrfs block-size: 4096 B dev: /dev/nvme1n1p6
maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 93.9 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 dev: /dev/zram0
Sensors:
System Temperatures: cpu: 47.8 C mobo: 27.0 C
Fan Speeds (rpm): N/A
Info:
Memory: total: 96 GiB note: est. available: 93.9 GiB used: 10.28 GiB (10.9%)
Processes: 609 Power: uptime: 14h 46m states: freeze,mem,disk
suspend: deep avail: s2idle wakeups: 1 hibernate: platform avail: shutdown,
reboot, suspend, test_resume image: 37.45 GiB
services: power-profiles-daemon,upowerd Init: systemd v: 258
default: graphical tool: systemctl
Packages: 2015 pm: pacman pkgs: 1994 libs: 574 tools: octopi,paru,yay
pm: flatpak pkgs: 21 Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Bash (sudo)
v: 5.3.3 running-in: konsole inxi: 3.3.39
Garuda (2.8.3-2):
System install date:     2025-09-23
Garuda release:          250916
Last full system update: 2025-09-27
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       Yes
Failed units:
--- System Health Check Report ---
24/24 checks run in 0.32 seconds ⌛
Powered by garuda-health 🦅

✅ System health check passed. No issues found.
2

We need your garuda-inxi. We can not help you without this information, because we do not know what your setup is.

2 Likes
3

@CXDReaper Please do not move threads back to the wrong category after mods have already moved your thread to the right spot. Thanks.

1 Like
4

Heya. Could you please state what you have tried so far? What are the exact xrandr commands you have tried without success?

1 Like
5

Sorry about that, I thought the flair was changed, only because I didn’t include the garuda-inxi. Apologies, won’t happen again.

6

Howdy,

So, I tried different variations of;

xrandr --output DP-3 (along with trying other monitors to see if any difference happened)
xrandr --output DP-3 --primary --right-of DP-2 (I found this on a post that was linked from Reddit) https://askubuntu.com/questions/925303/how-to-set-primary-monitor-and-relation-between-monitors-on-ubuntu-using-termina

I also tried manually moving monitors in the display setup order, rebooting PC multiple times during the tests to make sure it didn’t have to relaunch the workspace or anything.

I can manually move the window via hotkeys to other windows, but it’s the wrong resolution as my left monitor that it likes putting it on is 1080p, where my others are 1440p

7

Oh, I also tried setting up a rule in Window Management as well. I was going to provide a screenshot, but it appears I cannot.

Window Class → Exact Match
Match Whole Window Class → No
Window Types → All Selected (all)
Position → Apply Initially → 2250 x 264
Size → Apply initially → 1671 x 981
Ignore Requested Geometry → Force

8

Try

xrandr --output XWAYLAND[X] --primary

Where [X] is replaced with a number starting at 0 up to how many displays you have.

9

Hmm… Perhaps I’m not understanding how to utilize this, I checked --help as well and am not seeing that XWAYLAND argument available. Is that just a global variable and we’re accessing the array? If so, still no dice. I ran it 2 different ways, thinking maybe it needs accessed as a variable;

─justinr@justin in ~
╰─λ xrandr --output XWAYLAND[3] --primary
warning: output XWAYLAND[3] not found; ignoring

justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND[2] --primary
warning: output XWAYLAND[2] not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND[1] --primary
warning: output XWAYLAND[1] not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND[0] --primary
warning: output XWAYLAND[0] not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr XWAYLAND
xrandr: unrecognized option 'XWAYLAND'
Try 'xrandr --help' for more information.

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output $XWAYLAND[0] --primary
fish: array indices start at 1, not 0.
xrandr --output $XWAYLAND[0] --primary
^

╭─justinr@justin in ~
[🔴] × xrandr --output $XWAYLAND[1] --primary
warning: output --primary not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output $XWAYLAND[2] --primary
warning: output --primary not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output $XWAYLAND[3] --primary
warning: output --primary not found; ignoring
10

it would be:

xrandr --output XWAYLAND0 --primary 
xrandr --output XWAYLAND1 --primary 
xrandr --output XWAYLAND2 --primary 
...

You will have to trial and error which display is the correct one.

1 Like
11

No difference in response…

justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND0 --primary
warning: output XWAYLAND0 not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND1 --primary
warning: output XWAYLAND1 not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND2 --primary
warning: output XWAYLAND2 not found; ignoring

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output XWAYLAND3 --primary
warning: output XWAYLAND3 not found; ignoring
12

May you run
xrandr

without any extra flags and post the output here?

13

Here you go sir;

╭─justinr@justin in ~ took 0s
╰─λ xrandr
Screen 0: minimum 16 x 16, current 7040 x 1649, maximum 32767 x 32767
DP-1 connected 2560x1440+4480+209 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440    164.78*+
1920x1440    164.80
1600x1200    164.75
1440x1080    164.78
1400x1050    164.80
1280x1024    164.68
1280x960     164.67
1152x864     164.60
1024x768     164.78
800x600      164.38
640x480      164.26
320x240      163.69
1920x1200    164.78
1680x1050    164.78
1440x900     164.61
1280x800     164.65
1152x720     164.57
960x600      164.43
928x580      164.51
800x500      164.25
768x480      164.47
720x480      164.18
640x400      164.01
320x200      161.83
2048x1152    164.69
1920x1080    164.82
1600x900     164.66
1368x768     164.67
1280x720     164.53
1024x576     164.65
864x486      164.71
720x400      164.23
640x350      164.46
DP-3 connected primary 2560x1440+1920+0 (normal left inverted right x axis y axis) 697mm x 392mm
2560x1440    239.88*+
1920x1440    239.90
1600x1200    239.94
1440x1080    239.87
1400x1050    239.76
1280x1024    239.78
1280x960     239.80
1152x864     239.87
1024x768     239.74
800x600      239.81
640x480      239.72
320x240      238.24
1920x1200    239.94
1680x1050    239.81
1440x900     239.80
1280x800     239.70
1152x720     239.91
960x600      239.72
928x580      239.78
800x500      239.72
768x480      239.72
720x480      239.35
640x400      239.49
320x200      238.84
2048x1152    239.87
1920x1080    239.88
1600x900     239.83
1368x768     239.74
1280x720     239.96
1024x576     239.43
864x486      239.60
720x400      239.62
640x350      239.59
DP-2 connected 1920x1080+0+209 (normal left inverted right x axis y axis) 597mm x 336mm
1920x1080    143.88*+
1440x1080    143.80
1400x1050    143.89
1280x1024    143.79
1280x960     143.86
1152x864     143.92
1024x768     143.87
800x600      143.83
640x480      143.85
320x240      142.05
1680x1050    143.88
1440x900     143.86
1280x800     143.84
1152x720     143.77
960x600      143.72
928x580      143.50
800x500      143.68
768x480      143.69
720x480      143.85
640x400      143.37
320x200      141.40
1600x900     143.93
1368x768     143.77
1280x720     143.67
1024x576     143.91
864x486      143.63
720x400      143.88
640x350      143.57
14

Can you go ahead and try this?

xrandr --output DP-1 --primary
# OR
xrandr --output DP-2 --primary
# OR
xrandr --output DP-3 --primary

to try and change the primary display?

1 Like
15

I will try this one again, but that is one of the original steps I took in attempting to get this to work before posting on this forum. One moment

16

It takes the commands with the arguments without any errors, however, there is no change in attempting to open any games. I tried all, for good measure, however, the proper display in my case would be DP-3

─justinr@justin in ~ took 0s
╰─λ xrandr --output DP-3 --primary

╭─justinr@justin in ~
╰─λ xrandr --output DP-2 --primary

╭─justinr@justin in ~ took 0s
╰─λ xrandr --output DP-1 --primary
17

Sorry, I’m a bit out of my depth then. I assume these games are using proton? I’m not really familiar with the details there. I hope someone else can help with this!

1 Like
18

No worries, I appreciate the help. Some of them are Proton, some are native.

2 Likes
19

Think on it, default steam games run on the “main” monitor.
In some games you find settings to switch the monitor.

This ?
SUPER + Shift + Left Arrow key
or
SUPER + Shift + Right Arrow key
or you use first “window mode” (game) then switch to your “game” monitor ?

and sorry, i mean xrandr under wayland is not function.
For this you need to login in a X11 session.

2 Likes
20

Right, that’s the issue, yes. They are opening on the incorrect monitor, not the “main” monitor.

And yes, the hotkeys to move a window to another monitor. The games that I am testing with do not have an option within the game to change the monitor, as that would have been a simple fix.

I definitely won’t be using X11, as I have 3 monitors with different refresh rates.

Thanks!