My problem is similar, but differs for specifics. I have an ASUS ROG Strix G615LR laptop with an Nvidia 5070 TI. My laptop keyboard works fine when I haven’t launched a Steam game. Whenever I launch Diablo IV i lose the ‘c’, ‘v’ and ‘esc’ keys completely (as in no input from the keys). In addition, other key entries sometime repeat rapidly (after initially touching them). Pressing the backspace key can remove one or all of the key entries, again in rapid succession.
This all started after updating CachyOS to kernel 6.18. My build and laptop information:
Operating System: CachyOS Linux
KDE Plasma Version: 6.6.5
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1
Kernel Version: 6.18.33-2-cachyos-lts (64-bit)
Graphics Platform: Wayland
Processors: 24 × Intel® Core™ Ultra 9 275HX
Memory: 32 GiB of RAM (30.7 GiB usable)
Graphics Processor 1: Intel® Graphics
Graphics Processor 2: NVIDIA GeForce RTX 5070 Ti Laptop GPU
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Strix G16 G615LR_G615LR
System Version: 1.0
I’ve also found that slowing the keyboard delay and repeat rates does not resolve the issue, so it is not an input lag problem.
If I shut down the game and close Steam, my laptop keyboard functions as normal.
However, if I alt-tab out of Diablo IV and try typing - such as in a search window in my browser app - the same keyboard issues noted in the game follow (ie no ‘c’, ‘v’ or ‘esc’ key inputs and the rapid letter repeats or deletion of key entries). After alt-tabbing out of the game, closing Diablo IV and Steam down doesn’t restore the normal keyboard functions/responses, it stays bugged.
At that point, if I try rebooting I still have no ‘c’, ‘v’ or ‘esc’ keys input response. The only way to I’ve found to restore full keyboard function is to perform an EC reset.
At this point I’d love to stick with the updated kernel, as builds before 6.18 don’t appear to work with ASUS ROG Control Center, but if it means every time I try to play a game on Steam I’m rolling the dice on whether or not my laptop’s keyboard input is going to fully work, then I may have to rollback to a pre-6.18 kernel build.
Would appreciate any assistance on this issue, or if someone else who’s having the same or similar problems has a work-around.