Skip to content
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

Touchscreen on Steam Deck (OLED?) is misbehaving in non-Steam games. #328

Open
Naxdy opened this issue Apr 23, 2024 · 5 comments
Open

Touchscreen on Steam Deck (OLED?) is misbehaving in non-Steam games. #328

Naxdy opened this issue Apr 23, 2024 · 5 comments
Labels
1. type: bug Something isn't working 2. priority: 2. normal 3. status: waiting on further information Further information is requested ❗ help wanted Extra attention is needed

Comments

@Naxdy
Copy link

Naxdy commented Apr 23, 2024

On my Steam Deck OLED I'm having an issue in non-steam games where the touchscreen is misbehaving in the following way: Whenever a touch is input, it registers that touch where the cursor was last let go, instead of the location I actually touched. Furthermore, the cursor has to be dragged before being let go, for the "location change" to be registered.

NOTE: The touchscreen is behaving normally in Gamescope and in the desktop environment (Plasma 6). Steam-native games have not yet been tested. Non-Steam games exhibit the erratic behavior described above.

@Naxdy
Copy link
Author

Naxdy commented Apr 23, 2024

Also, not sure if it makes a difference, but so far I've tested only Qt6 apps: Citra, qpwgraph, Dolphin Emulator

@Naxdy
Copy link
Author

Naxdy commented May 2, 2024

This problem was solved, at least for me, by adding gnome.caribou to environment.systemPackages

Perhaps this should be included by default?

@samueldr
Copy link
Member

Hi, sorry it took a while until you got a response.

You've stated in non-Steam games, but just to be clear, that is in non-Steam games running in the Steam session, right?

On my systems, I can't see that behaviour happening. Though I also have heard some users on the LCD model have had issues with touch in games. So I'm wondering if there's a common element here.

And I suppose you meant more that adding gnome.caribou to environment.systemPackages was a workaround. It's more likely it's not directly that package, but a side-effect from ambient impurities that helps here.

(And I suppose it's possible that the bug comes from another ambient impurity, or that I myself in my non-gnome non-plasma end-up with the same or another impurity that makes me not observe any issue.)

@samueldr samueldr added 1. type: bug Something isn't working ❗ help wanted Extra attention is needed 3. status: waiting on further information Further information is requested 2. priority: 2. normal labels Oct 27, 2024
@Naxdy
Copy link
Author

Naxdy commented Oct 27, 2024

Greetings, no worries.

You've stated in non-Steam games, but just to be clear, that is in non-Steam games running in the Steam session, right?

Yes, correct.

It's also possible that the bug "fixed itself" some other way just around the same time I happened to add caribou. The device is out of my hands now however (got it as a gift for someone) so tracing this will be a bit difficult for me now. What matters to me is that now it works :p

@samueldr
Copy link
Member

Thank you for coming back to me much quicker than me to you 😅.

Alright, I'll consider this "blocked" until further information comes from anyone with any model Steam Deck is seeing issues with touch, only in non-steam games. Only because I don't know how to make it fail at the moment.

@samueldr samueldr changed the title Touchscreen on Steam Deck OLED is misbehaving in non-Steam games. Touchscreen on Steam Deck (OLED?) is misbehaving in non-Steam games. Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. type: bug Something isn't working 2. priority: 2. normal 3. status: waiting on further information Further information is requested ❗ help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants