[FIXED] Keyboard not working in Linux

[Orzgorth]

I can launch the game but I'm unable to move using the keyboard in Linux. Is anyone else having this problem?

[Spider]

Hi fellow traveler Orzgorth,

It seems to be working for me currently; though maybe I can help as it may depend on your environment. I'm not one of the devs for the game but I'd be glad to test something closer to your setup (if possible) or see if I can offer any thoughts.

1. Which Linux Distro and version are you using?
   
2. What graphical environment? (GNOME3, KDE, other?)
   
3. Are you using (X)wayland or Xorg for your session? Multiple monitors?
   
4. Do you normally have an alternate keyboard layout (azerty, us, dvoark, etc)?
   
5. Has it worked on your system in the past?
   
6. Did you choose the default option when launching it, or the modable/32bit etc?
   
7. Do the up/down/left/right arrow keys (not WASD) work at the menus before starting a game and getting the first-person view, or are those not working at the menu either?
   
8. What GPU or general specs (likely this is less critical at the moment)
   
9. (Oh, also do you have any controller or sort of device that may be detected as a gamepad that is connected? I haven't tried connecting one yet but maybe disconnect that before starting just is case it takes over or causes an issue somehow or is sending spurious events.

---

My test vm with vfio passthrough (video+usb_keyboard) that is working (minimal changes):

• Fedora 37 fully updated; Gnome3 with Xorg
  
• Worked with dvorak/us keyboard layout choices
  • (ignores dvorak and is using scancodes/something, so even if dvorak is set, WASD works w/o keybinding changes, and setting keys results in the usual US qwerty layout letter)
    
  • (usually I have ibus setup with a few east asian input methods but not on this more basic test test VM)
• This is the first time I've launched it and I picked the default option.
  
• Unfortunately my test GPU is and older nvidia card which doesn't support wayland so I can't easily test that currently.

I tried with the linux native version and used the default game settings of fullscreen and alt-tab didn't break it, and then tried with windowed as well and that seemed ok.

Also, I happen to have all the DLC but I've not tested any of them but they were installed. I highly doubt it would make a difference when launching and running the base Talos Principle game but wanted to note it just in case. I'm not suggesting you get any dlc to fix things, but want to be sure of if you are running the base game or one of the other options?

---

It's possible there could be an issue within a wayland session or another desktop environment or distro, so some specifics like the questions above may help to decide on good things to test out, or may allow me to try to test another distro when I have a moment.

Let's try to clarify the questions above (if not sure feel free to ask for clarifications and I can be more specific) and I may be able to test with your distro later. It may also be worth choosing a different desktop session type like Xorg (if using wayland) or consider another desktop environment if you have multiple on hand, usually chosen from the login screen after picking your user but before entering a password (usually a gear icon or something elsewhere on the login-manager screen). Again, I can give specific steps/etc but wanted to toss out a few ideas before I return in case you're familiar.

[Orzgorth]

The keyboard issue is fixed! It was working before I updated the Steam Runtime I think. There was a recent Steam Runtime update and I suppose that fixed it? I'm not sure. Anyway,

@Spider thank you for being so thorough! Next time I post a question I'll make sure to add all the details you've asked for.

[Spider]

Originally posted by Orzgorth:

The keyboard issue is fixed! It was working before I updated the Steam Runtime I think. There was a recent Steam Runtime update and I suppose that fixed it? I'm not sure. Anyway,

Nice, I'm glad it's working now! Thanks for following up and with what seemed to resolve it. I passingly saw a bunch of the recent Steam client change notes in that general area and wondered. I didn't catch anything directly obvious, but also hadn't gone poking on github for any recent specifics for those that might be there.

Originally posted by Orzgorth:

@Spider thank you for being so thorough! Next time I post a question I'll make sure to add all the details you've asked for.

No worries, it can help with a head start, or help passerby in the future, or so someone with a similar setup knows it may be more relevant/valuable to test/reply sooner. (and better guides any word-of-mouth and any trickle-back from reaching out to other networks, including known/found issues unrelated to Steam/Talos or others with a similar issue that's (un)resolved.) If it's ever many people reporting an issue then it helps to start seeing if it's distro/version specific, etc.

So while it's definitely helpful to provide those details upfront, sometimes it's enough to just initially get eyes on the question sooner. I added some targeted questions and few maybe less relevant (but just in case, and to avoid potential delay in back-and-forth), but the distro(+version), graphical environment, wayland/xorg and gpu are best, and sometimes the other hardware and details based on the given issue; as you probably suspect. :) Any extra details you think of for future issues can be good though and I'm sure others that are curious or are looking to help will appreciate it too, including any devs wondering about reproduction/frequency of an issue.

In a way, if I had a moment to test beyond the distro I had on hand when I first saw your comment, then not having the info may have saved some time, like in cases where it eventually got resolved and I've not confirmed first before starting to get ready to test (that would be a Spider-specific choice/induced problem of which I'm aware, though; and not your burden/responsibility, haha.) Potential keyboard/input issues could be relevant for me so I was also curious.

Thanks again for the follow-up and thoughtfulness. Enjoy!