this post was submitted on 18 Feb 2024
36 points (97.4% liked)

Steam Deck

14850 readers
30 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Link to our Matrix Space

founded 3 years ago
MODERATORS
 

My on-screen keyboard in desktop mode has somehow become undocked and wider than the screen, making it hard to press certain keys which are half off-screen. It still works otherwise - I can open the keyboard by pressing X and close the keyboard by pressing L4.

I don't know how this has happened in the first place, and I can't find a setting for it in Steam. Any idea how I can reset the keyboard position?

you are viewing a single comment's thread
view the rest of the comments
[–] weston@techhub.social 8 points 9 months ago (3 children)

@galmuth @steamdeck I have the same issue, are you on the latest beta? I think it’s a beta bug.

[–] MossyFeathers@pawb.social 6 points 9 months ago

I'm on the stable branch and have this issue, so not a beta bug.

[–] galmuth@feddit.uk 3 points 9 months ago

I am currently on the latest beta - I'll test the stable/preview channels in case that makes a difference.

[–] galmuth@feddit.uk 3 points 9 months ago

Well, it looks like reverting to Stable seemed to at least partially fix it for me. The keyboard is still higher on the screen, but at least it fits to the screen width correctly. Thanks!

I couldn't find any mention of anyone else with this issue around the web or on valve's GitHub issue tracker, so I assumed it was something dumb I'd done rather than a bug.