From 5f4cc402666db733627ff47ebc9c73f736b18e22 Mon Sep 17 00:00:00 2001 From: Isaac Corbrey Date: Sat, 15 Aug 2026 09:55:11 -0400 Subject: [PATCH] niri: Don't screw up xwayland-satellite with non-0,0 monitors --- hosts/elysium/niri/config.kdl | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/hosts/elysium/niri/config.kdl b/hosts/elysium/niri/config.kdl index 8104adf..d3e19c6 100644 --- a/hosts/elysium/niri/config.kdl +++ b/hosts/elysium/niri/config.kdl @@ -16,11 +16,21 @@ // gameLatencyTweaks.enable in modules/home/niri/default.nix) is on that // output, so the desktop keeps a stable refresh and only games/video flip // VRR on. +// DP-1 is pinned at the coordinate origin (0,0) deliberately, not just +// left-to-right order. xwayland-satellite has an open upstream bug where +// X11/Xwayland clients on an output with a non-zero logical position get +// corrupted absolute pointer coordinates (observed here as every click +// after fullscreen pointer-confinement engaging landing at the output's +// edge pixel, regardless of actual cursor position). Giving the output we +// actually game on the (0,0) origin sidesteps the bug for that output. +// HDMI-A-2 and DP-2 sit at negative/positive offsets and would still be +// exposed to the same defect if a game ran there instead. +// Upstream: https://github.com/Supreeeme/xwayland-satellite/issues/66 output "HDMI-A-2" { mode "2560x1440@144.000" scale 1.0 transform "normal" - position x=0 y=0 + position x=-2560 y=0 variable-refresh-rate on-demand=true } @@ -28,7 +38,7 @@ output "DP-1" { mode "2560x1440@179.999" scale 1.0 transform "normal" - position x=2560 y=0 + position x=0 y=0 variable-refresh-rate on-demand=true } @@ -36,6 +46,6 @@ output "DP-2" { mode "2560x1440@179.999" scale 1.0 transform "normal" - position x=5120 y=0 + position x=2560 y=0 variable-refresh-rate on-demand=true } -- 2.51.2