[GH-ISSUE #217] Left shift and left control not working when connecting #145

Closed
opened 2026-10-15 12:57:08 +00:00 by bsakaguchi · 10 comments
Owner

Originally created by @JakubBlaszczyk on GitHub (Jun 27, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/217

Hi,

I have a proxmox set up with docker.
I connect to it with Windows machine and open gow steam image.
When I run game from Steam I have issue that left shift and left control are not working. I have tested it with Stellar Blade, Factorio, Baldurs Gate 3 and Marvel Rivals on two separate Windows machines.
I can open steam overlay using left shift and tab so it might be that key combinations are working.
This issue does not happen on macOS, I haven't tested it on linux.

Wolf setup.

docker run \
    --name wolf \
    --network=host \
    -e XDG_RUNTIME_DIR=/tmp/sockets \
    -v /tmp/sockets:/tmp/sockets:rw \
    -e HOST_APPS_STATE_FOLDER=/etc/wolf \
    -e WOLF_INTERNAL_MAC=B6:1E:50:36:45:BB \
    -e WOLF_RENDER_NODE=/dev/dri/renderD128 \
    -v /etc/wolf:/etc/wolf:rw \
    -v /var/run/docker.sock:/var/run/docker.sock:rw \
    --device /dev/dri/ \
    --device /dev/uinput \
    --device /dev/uhid \
    -v /dev/:/dev/:rw \
    -v /mnt/udev:/run/udev:rw \
    -v /rpool/data/subvol-100-disk-0/srv/share:/mnt/share:rw \
    --device-cgroup-rule "c 13:* rmw" \
    ghcr.io/games-on-whales/wolf:stable

Default steam configuration in /etc/wolf/cfg/config.toml.

Logs from WolfSteam container

Errors from xkbcomp are not fatal to the X server

(/usr/libexec/xdg-desktop-portal:228): xdg-desktop-portal-WARNING **: 00:04:37.174: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory

(/usr/libexec/xdg-desktop-portal:228): xdg-desktop-portal-WARNING **: 00:04:37.174: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op ChangeProperty (no minor), code Window (no extension), sequence 401, value 6291459
00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op DeleteProperty (no minor), code Window (no extension), sequence 402, value 6291459
00:00:30.386 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op ChangeProperty (no minor), code Window (no extension), sequence 1403, value 75497473
00:00:30.386 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op DeleteProperty (no minor), code Window (no extension), sequence 1404, value 75497473
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
> Warning:          Could not resolve keysym XF86KbdInputAssistPrevgrou
> Warning:          Could not resolve keysym XF86KbdInputAssistNextgrou
Errors from xkbcomp are not fatal to the X server
Originally created by @JakubBlaszczyk on GitHub (Jun 27, 2025). Original GitHub issue: https://github.com/games-on-whales/wolf/issues/217 Hi, I have a proxmox set up with docker. I connect to it with Windows machine and open gow steam image. When I run game from Steam I have issue that left shift and left control are not working. I have tested it with Stellar Blade, Factorio, Baldurs Gate 3 and Marvel Rivals on two separate Windows machines. I can open steam overlay using left shift and tab so it might be that key combinations are working. This issue does not happen on macOS, I haven't tested it on linux. Wolf setup. ``` docker run \ --name wolf \ --network=host \ -e XDG_RUNTIME_DIR=/tmp/sockets \ -v /tmp/sockets:/tmp/sockets:rw \ -e HOST_APPS_STATE_FOLDER=/etc/wolf \ -e WOLF_INTERNAL_MAC=B6:1E:50:36:45:BB \ -e WOLF_RENDER_NODE=/dev/dri/renderD128 \ -v /etc/wolf:/etc/wolf:rw \ -v /var/run/docker.sock:/var/run/docker.sock:rw \ --device /dev/dri/ \ --device /dev/uinput \ --device /dev/uhid \ -v /dev/:/dev/:rw \ -v /mnt/udev:/run/udev:rw \ -v /rpool/data/subvol-100-disk-0/srv/share:/mnt/share:rw \ --device-cgroup-rule "c 13:* rmw" \ ghcr.io/games-on-whales/wolf:stable ``` Default steam configuration in /etc/wolf/cfg/config.toml. Logs from WolfSteam container ``` Errors from xkbcomp are not fatal to the X server (/usr/libexec/xdg-desktop-portal:228): xdg-desktop-portal-WARNING **: 00:04:37.174: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory (/usr/libexec/xdg-desktop-portal:228): xdg-desktop-portal-WARNING **: 00:04:37.174: Realtime error: Could not get pidns: Could not fstatat ns/pid: Not a directory 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1192] Failed to get window property 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op ChangeProperty (no minor), code Window (no extension), sequence 401, value 6291459 00:00:16.028 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op DeleteProperty (no minor), code Window (no extension), sequence 402, value 6291459 00:00:30.386 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op ChangeProperty (no minor), code Window (no extension), sequence 1403, value 75497473 00:00:30.386 [ERROR] [wlr] [xwayland/xwm.c:1633] xcb error: op DeleteProperty (no minor), code Window (no extension), sequence 1404, value 75497473 The XKEYBOARD keymap compiler (xkbcomp) reports: > Warning: Unsupported maximum keycode 708, clipping. > X11 cannot support keycodes above 255. > Warning: Could not resolve keysym XF86KbdInputAssistPrevgrou > Warning: Could not resolve keysym XF86KbdInputAssistNextgrou Errors from xkbcomp are not fatal to the X server ```
Author
Owner

@JakubBlaszczyk commented on GitHub (Jun 29, 2025):

Update:
1: On MacOS it is also not working.
2: In Marvel Rivals left shift was working in chat (when typing capital letters) and in game options (to assign buttons for specific actions) but it didn't work when playing the game.

<!-- gh-comment-id:3017236638 --> @JakubBlaszczyk commented on GitHub (Jun 29, 2025): Update: 1: On MacOS it is also not working. 2: In Marvel Rivals left shift was working in chat (when typing capital letters) and in game options (to assign buttons for specific actions) but it didn't work when playing the game.
Author
Owner

@ABeltramo commented on GitHub (Jun 30, 2025):

Thanks for all the details, just to re-iterate what has been discussed in Discord:

  • Can you confirm that using ghcr.io/games-on-whales/steam:sha-5006e1b doesn't present any issue?
  • Could you try running Gamescope instead of Sway by changing this line in the config.toml to be RUN_GAMESCOPE=1?

I'm just trying to narrow down the issue, if it's just a regression in Sway since we've updated to the latest then it should be easy to fix it. If it's a more general Proton issue then it might be a bit more tricky..

<!-- gh-comment-id:3020038815 --> @ABeltramo commented on GitHub (Jun 30, 2025): Thanks for all the details, just to re-iterate what has been discussed in Discord: - Can you confirm that using `ghcr.io/games-on-whales/steam:sha-5006e1b` doesn't present any issue? - Could you try running Gamescope instead of Sway by changing [this line](https://github.com/games-on-whales/wolf/blob/76d0c25f40544739ee526ee1b5547d12001f536c/src/moonlight-server/state/default/config.v4.toml#L76) in the `config.toml` to be `RUN_GAMESCOPE=1`? I'm just trying to narrow down the issue, if it's just a regression in Sway since we've updated to the latest then it should be easy to fix it. If it's a more general Proton issue then it might be a bit more tricky..
Author
Owner

@JakubBlaszczyk commented on GitHub (Jun 30, 2025):

I have checked and it is working properly on ghcr.io/games-on-whales/steam:sha-5006e1b.

By default I was using ghcr.io/games-on-whales/steam:edge and when I have replaced RUN_SWAY=true with RUN_GAMESCOPE=1 it did not help and it caused strange behavior.

When I moved my mouse (which moves my camera) to the sides after around 45 degrees, camera started moving vertically instead of horizontally. I have only checked this in Stellar Blade. If you need more samples then I can verify on more games.

<!-- gh-comment-id:3020416739 --> @JakubBlaszczyk commented on GitHub (Jun 30, 2025): I have checked and it is working properly on ```ghcr.io/games-on-whales/steam:sha-5006e1b```. By default I was using ```ghcr.io/games-on-whales/steam:edge``` and when I have replaced ```RUN_SWAY=true``` with ```RUN_GAMESCOPE=1``` it did not help and it caused strange behavior. When I moved my mouse (which moves my camera) to the sides after around 45 degrees, camera started moving vertically instead of horizontally. I have only checked this in Stellar Blade. If you need more samples then I can verify on more games.
Author
Owner

@ABeltramo commented on GitHub (Jun 30, 2025):

when I have replaced RUN_SWAY=true with RUN_GAMESCOPE=1 it did not help and it caused strange behavior.

Did it change anything on the original issue about the left CTRL/SHIFT ?

<!-- gh-comment-id:3020463800 --> @ABeltramo commented on GitHub (Jun 30, 2025): > when I have replaced RUN_SWAY=true with RUN_GAMESCOPE=1 it did not help and it caused strange behavior. Did it change anything on the original issue about the left CTRL/SHIFT ?
Author
Owner

@JakubBlaszczyk commented on GitHub (Jun 30, 2025):

No, it did not help with CTRL/SHIFT.

<!-- gh-comment-id:3020586907 --> @JakubBlaszczyk commented on GitHub (Jun 30, 2025): No, it did not help with CTRL/SHIFT.
Author
Owner

@ABeltramo commented on GitHub (Jul 1, 2025):

I've just pushed a potential fix for this, basically reverting back Sway to 1.9. When you've got a chance could you try pulling the latest

docker pull ghcr.io/games-on-whales/steam:edge

(remember to put back the RUN_SWAY=1 in config.toml) and let me know how it goes!

<!-- gh-comment-id:3025266738 --> @ABeltramo commented on GitHub (Jul 1, 2025): I've just pushed a potential fix for this, basically reverting back Sway to 1.9. When you've got a chance could you try pulling the latest ``` docker pull ghcr.io/games-on-whales/steam:edge ``` (remember to put back the `RUN_SWAY=1` in `config.toml`) and let me know how it goes!
Author
Owner

@JakubBlaszczyk commented on GitHub (Jul 2, 2025):

Yes, it is working. Thank you a lot for help!

<!-- gh-comment-id:3029195322 --> @JakubBlaszczyk commented on GitHub (Jul 2, 2025): Yes, it is working. Thank you a lot for help!
Author
Owner

@ABeltramo commented on GitHub (Jul 2, 2025):

Glad that's fixed! Have fun!

<!-- gh-comment-id:3029218470 --> @ABeltramo commented on GitHub (Jul 2, 2025): Glad that's fixed! Have fun!
Author
Owner

@BlauerHunger commented on GitHub (Jul 8, 2025):

I had this issue with prismlauncher and it's also fixed there with the mentioned change. Thank you!

<!-- gh-comment-id:3049524285 --> @BlauerHunger commented on GitHub (Jul 8, 2025): I had this issue with prismlauncher and it's also fixed there with the mentioned change. Thank you!
Author
Owner

@Abalthazarr commented on GitHub (Aug 14, 2025):

could replicate this on the xfce desktop with the nvidia-manual version

<!-- gh-comment-id:3187105307 --> @Abalthazarr commented on GitHub (Aug 14, 2025): could replicate this on the xfce desktop with the nvidia-manual version
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
games-on-whales/wolf#145
No description provided.