Keyboard input keys "sticking" in certain games

[Nandor]

Currently happening with only a couple of games; Planet Crafter and Sunkenland. Started within the past week or so and I'm not sure what change or update could've caused it as the kernel and Proton versions I'd been using hasn't changed, but I tried a previous kernel as well as a previous version of Proton and it made no difference.

The issue is that the games aren't seeing when I release the key and pressing other keys doesn't stop it, I have to press the same "stuck" key for it to stop being stuck. I play a number of other games, all using the same Proton, and they have no issue.

I'm using proton-cachyos-10.0-20260321-slr-x86_64_v3 currently but -20260203-slr-x86_64 has the same issue and was working fine for the past 1+ month so I don't see how it could be a Proton issue.

Not using Flatpak Steam.

Booted the previous kernel (6.17.0-14-generic) that has been installed since November and it didn't help either. I can cope currently but it's annoying enough that it makes me not want to play these games until I can find a fix.

$ echo $XDG_SESSION_TYPE
x11

$ sudo inxi -Fxz
System:
Kernel: 6.17.0-19-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0
Desktop: Cinnamon v: 6.6.7 Distro: Linux Mint 22.3 Zena
base: Ubuntu 24.04 noble
Machine:
Type: Desktop System: ASRock product: X670E PG Lightning v: N/A serial: N/A
Mobo: ASRock model: X670E PG Lightning serial: <filter> UEFI: American
Megatrends LLC. v: 3.50 date: 09/18/2025
Battery:
ID-1: hidpp_battery_0 charge: 100% condition: N/A volts: 4.2 min: N/A
model: Logitech G903 LIGHTSPEED Wireless Gaming Mouse w/ HERO status: full
CPU:
Info: 12-core model: AMD Ryzen 9 7900X bits: 64 type: MT MCP MCM arch: Zen 4
rev: 2 cache: L1: 768 KiB L2: 12 MiB L3: 64 MiB
Speed (MHz): avg: 4115 high: 4966 min/max: 415/5738 boost: enabled cores:
1: 4965 2: 4965 3: 4966 4: 4965 5: 4966 6: 4965 7: 3007 8: 4839 9: 3007
10: 3007 11: 3007 12: 3007 13: 4965 14: 4966 15: 4966 16: 4966 17: 4962
18: 4343 19: 3007 20: 3007 21: 3583 22: 3007 23: 3007 24: 4333
bogomips: 225189
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900M]
vendor: Sapphire PULSE driver: amdgpu v: 6.16.6 arch: RDNA-3 bus-ID: 03:00.0
Device-2: AMD Raphael vendor: ASRock driver: amdgpu v: 6.16.6 arch: RDNA-2
bus-ID: 1a:00.0 temp: 42.0 C
Device-3: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
bus-ID: 7-2:3
Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 24.1.6 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
gpu: amdgpu resolution: 5120x1440~240Hz
API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
active: gbm,x11,surfaceless,device inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: PPA glx-v: 1.4
direct-render: yes renderer: Radeon RX 7900 XTX (radeonsi navi31 LLVM
20.1.8 DRM 3.64 6.17.0-19-generic)
API: Vulkan v: 1.3.275 drivers: N/A surfaces: xcb,xlib devices: 3
Audio:
Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel v: kernel
bus-ID: 03:00.1
Device-2: Creative Labs CA0132 Sound Core3D [Sound Blaster Recon3D /
Z-Series BlasterX AE-5 Plus] driver: snd_hda_intel v: kernel
bus-ID: 0d:00.0
Device-3: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
v: kernel bus-ID: 1a:00.1
Device-4: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel
v: kernel bus-ID: 1a:00.6
Device-5: Logitech G733 Gaming Headset
driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 3-2:2
Device-6: Logitech Webcam C930e driver: snd-usb-audio,uvcvideo type: USB
bus-ID: 7-2:3
API: ALSA v: k6.17.0-19-generic status: kernel-api
Server-1: PipeWire v: 1.0.5 status: n/a (root, process)
Network:
Device-1: Realtek RTL8125 2.5GbE vendor: ASRock driver: r8169 v: kernel
port: e000 bus-ID: 10:00.0
IF: enp16s0 state: up speed: 2500 Mbps duplex: full mac: <filter>
IF-ID-1: br-9abb8a34c0a7 state: down mac: <filter>
IF-ID-2: docker0 state: down mac: <filter>
Bluetooth:
Device-1: TP-Link UB500 Adapter driver: btusb v: 0.8 type: USB
bus-ID: 1-12:5
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.1
lmp-v: 10
Drives:
Local Storage: total: 7.28 TiB used: 2.16 TiB (29.7%)
ID-1: /dev/nvme0n1 vendor: Western Digital model: WD BLACK SN850X 4000GB
size: 3.64 TiB temp: 39.9 C
ID-2: /dev/nvme1n1 vendor: Western Digital model: WD BLACK SN850X 4000GB
size: 3.64 TiB temp: 46.9 C
Partition:
ID-1: / size: 3.58 TiB used: 1.08 TiB (30.3%) fs: ext4 dev: /dev/nvme1n1p2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat
dev: /dev/nvme1n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 4 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 34.0 C mobo: 40.0 C
Fan Speeds (rpm): fan-1: 924 fan-2: 0 fan-3: 954 fan-4: 918 fan-5: 919
fan-7: 918
GPU: device: amdgpu temp: 42.0 C device: amdgpu temp: 59.0 C fan: 579
Info:
Memory: total: 64 GiB note: est. available: 61.89 GiB used: 7.87 GiB (12.7%)
Processes: 595 Uptime: 32m Init: systemd target: graphical (5)
Packages: 3216 Compilers: gcc: 13.3.0 Shell: Sudo v: 1.9.15p5 inxi: 3.3.34

 

[Nandor]

I guess I'm on my own on this one.

 

[KGIII]

Sadly, it appears that nobody who saw your post has any ideas about how to fix it.

We normally frown on 'bumping' posts, but you've waited long enough for it to be acceptable. In fact, you've been patient for more than long enough. So, thanks for that.

This isn't something I'm familiar with. Your post tells me that you've already done everything I could think of. So, I can't help.

Heck, my first suggestion would be to try a different keyboard, but it appears to work just fine with other applications. So, that throws that out. You could still try it, but I wouldn't be able to explain why it solved the issue if it did solve the issue.

 

[osprey]

A few thoughts occur, but just investigative rather solutions.

I may have missed it from the inxi data which I combed through, but I didn't pick up what the actual keyboard is. For example, below shows the output with the keyboard using inxi here:

[~]$ inxi -J
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 16 rev: 2.0
  Hub-2: 1-2:2 info: ASMedia ASM1074 High-Speed hub ports: 4 rev: 2.1
  Device-1: 1-2.4:4 info: MediaTek Slim Portable DVD Writer
    type: mass storage rev: 2.0
  Device-2: 1-3:3 info: Logitech G512 RGB MECHANICAL GAMING KEYBOARD
    type: keyboard,HID rev: 2.0
  Device-3: 1-4:5 info: Logitech Mouse type: mouse rev: 2.0
  Device-4: 1-14:6 info: Intel AX211 Bluetooth type: bluetooth rev: 2.0
  Hub-3: 2-0:1 info: super-speed hub ports: 10 rev: 3.1
  Hub-4: 2-3:2 info: ASMedia ASM1074 SuperSpeed hub ports: 4 rev: 3.0

The output shows the "Logitech G512 RGB MECHANICAL GAMING KEYBOARD". Whatever your keyboard is, it may be worth searching online to see whether there are issues with that one that others have identified.

Is the Mint operating system upgraded to the latest possible upgrade? The xorg version on your machine appears to be 21.1.11, however there is a later one, 21.1.21, which is in use here on debian. Mint may however not have upgraded yet.

There are few different branded gaming style keyboards used here, and they don't all behave in identical ways, although the problem you described has not been experienced here. That's perhaps not helpful, other than to say that the most expensive gaming keyboard here (the one identified above) has been the best one in terms of functionality, though I don't personally play games, but others do here.

I don't know how useful it might be, but there are quite a few kernel parameters that can control keyboard issues. It's lower level intervention and prima facie would not seem relevant to this issue, but I mention it because it's related to keyboards. The parameters are here: https://docs.kernel.org/admin-guide/kernel-parameters.html. One can search for the term "keyboard" in the file to access the parameters and some descriptions of their effect.

 

[CaffeineAddict]

I guess I'm on my own on this one.

Sadly, it appears that nobody who saw your post has any ideas about how to fix it.

I didn't see this thread in Linux Gaming section until now and I'm sure I was checking the section.
Was it in approval queue IDK?

Some people here suggest connecting USB3 keyboard to USB3 port instead of into USB2, does your keyboard have USB3 port?
And another person claims it was their AV, do you have AV installed?

Comparing to other thread, one thing in common you have is Mint distro.

 

[KGIII]

Was it in approval queue IDK?

Nope. It went through the queue very quickly.

I'm not sure why you missed it, but it has been here since shortly after he first hit the post button. When it was new, I looked it over, but I couldn't think of anything that would help. After that, it was marked as read for me, so I didn't see it again until they bumped the thread.

I'm surprised they waited that long to at least try bumping it. If they'd done so, maybe 48 hours later, I would not have complained. If they kept bumping it over and over again, I'd have pointed out the futility of doing so.

This is just a good example where not everyone sees everything. It happens. Threads get missed by people who might be able to help.

Me? I use a very diligent (and consistent) method to go through all of the unread posts. This ensures that I see every existing thread. I skim a lot. There are some posters that I just barely read, mostly because they've shown me that I don't need to read their posts.

Basically, I use my scroll wheel's click to open threads in a new tab. I do a handful at a time. After doing that a couple of times, I hit the 'new post' link and keep going. I work my way through that. It's the second thing I do when I sign in for the day.

 

[Nandor]

Woah! Lots of action all at once. I'll go through in order.

@KGIII @osprey I'm using a Glorious GMMK 1 TKL which shows up as this...

Device-2: 1-10:4 info: Microdia Backlit Gaming Keyboard
type: keyboard,mouse rev: 2.0

I don't currently have a different keyboard I can test with, I'm using the cable supplied with the keyboard and while the keyboard port is USB-C it's only USB 2.0.

My Mint 22.3 install is fully up to date and xorg is still 21.1.11 according to inxi, but the packages themselves say 21.1.12.

I'll take a look at the kernel parameters for keyboards and see if there's anything that might be relevant.

@CaffeineAddict Not running any anti-virus, I am running OpenRGB which has had some compatibility issues with various hardware, however I have my keyboard excluded.

I'll try stopping apps/services that could possibly be interfering just to rule them out. EDIT: Stopped them, no change.

I also previously had my keyboard and mouse connected to a powered USB hub and connected them directly to the motherboard USB ports to rule out the hub being the issue, but since I have zero keyboard issues outside of a couple of games and no kernel messages logged that would indicate momentary device timeouts or disconnects I've mostly ruled out this being hardware.

I'd been considering replacing my keyboard, though not for any technical reason. I use a TKL for space and ergonomic reasons but have been eyeing the be quiet! Dark Mount as I do have a use for the numpad but not all the time, plus having dedicated media controls and Stream Deck-like keys combined with a web-based keyboard config tool that works with Linux is pretty compelling for me, but that's a different topic.

I wish I knew what was going on or what updated caused the issue, I have 40 hours in Planet Crafter and of those hours only the last 30 minutes or so of gameplay have had this issue. Sunkenland, which I started playing after this popped up in Planet Crafter, has had the issue since the start.

Also worth mentioning is that I recently enabled the ntsync module and thought that might've been the cause, but removing it made no difference.

 

[osprey]

Woah! Lots of action all at once. I'll go through in order.

@KGIII @osprey I'm using a Glorious GMMK 1 TKL which shows up as this...

Thanks for that info on the keyboard. Not being familiar with it, AI (gemini) had a few remarks which may be of interest which are in the spoiler.

There was a forum for glorious here: https://gloriousforum.com/t/gmmk-1-mini-led-and-performance-issues/13580, but it's closed and the advice on that site is to seek support at: www.gloriousgaming.com. At that latter site there's "live chat" and "email" but no forum. Can't say how helpful that would be.

Spoiler: AI output

Common problems with the Glorious GMMK 1 TKL keyboard include LED failures, software issues, and unresponsive keys, often linked to outdated legacy software. The GMMK 1 uses the "GMMK 1 Keyboard Editor" and is not compatible with the newer Glorious CORE software, which causes confusion and issues when updating firmware.
Common Issues

* LED/RGB Failures: Numerous reports indicate LEDs failing over time, either glowing in wrong colors or turning off completely.
* Software "Access Denied" & Detection: Users often face "Access is Denied" errors when running the legacy software, often due to mismatched serial numbers.
* Keyboard Freezing/Stopping: The keyboard can stop working entirely after launching the software or trying to update the firmware.
* Unresponsive Keys: Individual keys or entire rows may stop registering, which can sometimes be fixed by replacing the hot-swappable switch or re-seating them.
* Double Typing: Reports of switches (often the spacebar) double-tapping.

Troubleshooting & Fixes

* Reset to Factory Settings: Hold FN + ESC for 10 seconds, then press F1 + F3 + F5.
* Software Fixes: Run the GMMK 1 Legacy Software as an administrator.
* Bricked RGB Fix: If firmware updates break the RGB, you may need to use third-party tools like "Sonix Keyboard Flasher" to restore it.
* Switch Problems: Replace the hot-swappable switches on non-working keys.
* Use Proper Software: Ensure you are using the specific GMMK 1 Legacy Software and not the updated "Glorious CORE" (which is for newer products).

Important Notes

* The GMMK 1 is not compatible with Glorious CORE.
* The keyboard does not feature a USB passthrough port.

“The first time i just had the LED problem, then i reinstall de software and more LED's had de same problem and even some keys didn't work (switches are fine), then i uninstall everything restart my PC, restore the keyboard holding FN+R and all the keys...”
Gmmk 1 mini led and performance issues - Glorious Forum

Glorious Forum · 3 years ago
“I currently have 5 malfunctioning LEDs that either glow the wrong color or don't turn off. I contacted support that the keyboard can't be updated because the their software no longer supports this keyboard.”

 

[Nandor]

Thanks for that info on the keyboard. Not being familiar with it, AI (gemini) had a few remarks which may be of interest which are in the spoiler.

There was a forum for glorious here: https://gloriousforum.com/t/gmmk-1-mini-led-and-performance-issues/13580, but it's closed and the advice on that site is to seek support at: www.gloriousgaming.com. At that latter site there's "live chat" and "email" but no forum. Can't say how helpful that would be.

Spoiler: AI output

Common problems with the Glorious GMMK 1 TKL keyboard include LED failures, software issues, and unresponsive keys, often linked to outdated legacy software. The GMMK 1 uses the "GMMK 1 Keyboard Editor" and is not compatible with the newer Glorious CORE software, which causes confusion and issues when updating firmware.
Common Issues

* LED/RGB Failures: Numerous reports indicate LEDs failing over time, either glowing in wrong colors or turning off completely.
* Software "Access Denied" & Detection: Users often face "Access is Denied" errors when running the legacy software, often due to mismatched serial numbers.
* Keyboard Freezing/Stopping: The keyboard can stop working entirely after launching the software or trying to update the firmware.
* Unresponsive Keys: Individual keys or entire rows may stop registering, which can sometimes be fixed by replacing the hot-swappable switch or re-seating them.
* Double Typing: Reports of switches (often the spacebar) double-tapping.

Troubleshooting & Fixes

* Reset to Factory Settings: Hold FN + ESC for 10 seconds, then press F1 + F3 + F5.
* Software Fixes: Run the GMMK 1 Legacy Software as an administrator.
* Bricked RGB Fix: If firmware updates break the RGB, you may need to use third-party tools like "Sonix Keyboard Flasher" to restore it.
* Switch Problems: Replace the hot-swappable switches on non-working keys.
* Use Proper Software: Ensure you are using the specific GMMK 1 Legacy Software and not the updated "Glorious CORE" (which is for newer products).

Important Notes

* The GMMK 1 is not compatible with Glorious CORE.
* The keyboard does not feature a USB passthrough port.

“The first time i just had the LED problem, then i reinstall de software and more LED's had de same problem and even some keys didn't work (switches are fine), then i uninstall everything restart my PC, restore the keyboard holding FN+R and all the keys...”
Gmmk 1 mini led and performance issues - Glorious Forum

Glorious Forum · 3 years ago
“I currently have 5 malfunctioning LEDs that either glow the wrong color or don't turn off. I contacted support that the keyboard can't be updated because the their software no longer supports this keyboard.”

I have had firmware/LED issues in the past where the LED controlled was bricked but was able to fix them, that was a couple of years ago. Other than that the keyboard has been flawless. Thanks for digging around!

 

[Nandor]

Just a quick update, I tried a different keyboard and it's still happening.

 

[osprey]

Just a quick update, I tried a different keyboard and it's still happening.

If a second keyboard is doing the same thing, and that keyboard is known to be good, then that suggests that the issue of "games aren't seeing when I release the key" mentioned in post #1, is not a hardware one, but rather a software one.

On the keyboard it's possible to test the release events of keys in X or wayland using the command: xev. The command works in a terminal and opens up a window. After you move the mouse to the opened window, the terminal will output information on the keypress and the key release when you actually press a key. It outputs mouse events too, but they aren't the focus here. The following is the output when the key q has been pressed and released.

KeyPress event, serial 36, synthetic NO, window 0x400001,
    root 0x355, subw 0x0, time 34224535, (220,864), root:(1075,912),
    state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
    XLookupString gives 1 bytes: (71) "q"
    XmbLookupString gives 1 bytes: (71) "q"
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x400001,
    root 0x355, subw 0x0, time 34224608, (220,864), root:(1075,912),
    state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
    XLookupString gives 1 bytes: (71) "q"
    XFilterEvent returns: False

When you press a lot of different keys, if everything is working as intended, the same sort of result as the above output for each one should occur. That should let you know that keypress and key release are working. To exit xev, hit ctrl+c when the pointer is in the terminal.

For a full software check, the ultimate option is to re-install all of the relevant software, bearing in mind that the optimal state of the operating system is when it's upgraded to the latest possible version. That's pretty much all I can think of at the moment. For the details of the meaning of all the output variables one can check out the manual pages on xev, dumpkeys, keymaps etc. but for this exercise that may not be necessary.

 

[Nandor]

If a second keyboard is doing the same thing, and that keyboard is known to be good, then that suggests that the issue of "games aren't seeing when I release the key" mentioned in post #1, is not a hardware one, but rather a software one.

On the keyboard it's possible to test the release events of keys in X or wayland using the command: xev. The command works in a terminal and opens up a window. After you move the mouse to the opened window, the terminal will output information on the keypress and the key release when you actually press a key. It outputs mouse events too, but they aren't the focus here. The following is the output when the key q has been pressed and released.

KeyPress event, serial 36, synthetic NO, window 0x400001,
    root 0x355, subw 0x0, time 34224535, (220,864), root:(1075,912),
    state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
    XLookupString gives 1 bytes: (71) "q"
    XmbLookupString gives 1 bytes: (71) "q"
    XFilterEvent returns: False

KeyRelease event, serial 36, synthetic NO, window 0x400001,
    root 0x355, subw 0x0, time 34224608, (220,864), root:(1075,912),
    state 0x0, keycode 24 (keysym 0x71, q), same_screen YES,
    XLookupString gives 1 bytes: (71) "q"
    XFilterEvent returns: False

When you press a lot of different keys, if everything is working as intended, the same sort of result as the above output for each one should occur. That should let you know that keypress and key release are working. To exit xev, hit ctrl+c when the pointer is in the terminal.

For a full software check, the ultimate option is to re-install all of the relevant software, bearing in mind that the optimal state of the operating system is when it's upgraded to the latest possible version. That's pretty much all I can think of at the moment. For the details of the meaning of all the output variables one can check out the manual pages on xev, dumpkeys, keymaps etc. but for this exercise that may not be necessary.

Ran xev and not a single issue, however I have some good news! Apparently I didn't try an old enough version of Proton, I switched to Proton 9 for Planet Crafter and it worked flawlessly, not a single stuck key issue. I also poked around on ProtonDB and found someone with a completely different setup have the same problem and they were running Proton 10 as well.

I haven't tried Proton 9 with Sunkenland yet, but next time I play I'll give it a shot. Still super strange for it to work perfectly with Proton 10 and then start out of the blue. In any event, looks like Proton 9 is the fix here.