-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Touch input is wrong on multi-monitor configurations on Linux #2166
Comments
There appears to be widespread issues with touch mapping on multi-head Wayland systems, so we're removing this from the v0.22.0 milestone. See: Workaround: Disable the native pen/touch option on the Input tab. |
I found info about how to calibrate libinput touchscreen but couldn't do it: Right now I'm using next udev rule (touch input still broken): |
It seems this issue hasn't had any activity in the past 90 days. If it's still something you'd like addressed, please let us know by leaving a comment. Otherwise, to help keep our backlog tidy, we'll be closing this issue in 10 days. Thanks! |
This issue was closed because it has been stalled for 10 days with no activity. |
Just as another kind-of-workaround, if you connect to sunshine before connecting the additional monitors, touch input appears to work as expected (although it still has some artifacts which aren't present in single-monitor configurations). |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
Touch input is wrong when I have multiple monitors connected. No such issue on a single-monitor configuration
Expected Behavior
No response
Additional Context
sunshine_touch_bug.webm
Host Operating System
Linux
Operating System Version
Arch Linux KDE
Architecture
64 bit
Sunshine commit or version
sunshine-git nightly.dev.r214.g032680c-1
Package
Linux - AUR (Third Party)
GPU Type
AMD
GPU Model
RX 6700XT
GPU Driver/Mesa Version
Mesa 24.0.1-arch1.1
Capture Method (Linux Only)
KMS
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: