[SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

hlepme9 · 2024-11-14 12:11:33

What do I use?: KDE Plasma (Wayland)
My issue: Basically when I press keys they press twice if I type too fast or they glitch out and don't work I've replaced or re typed many keys while writing this, it's very annoying. Also for instance if I'm playing Minecraft and I hit the tab key it doesn't stay pressed, HELP ME. I've been trying to use linux and I don't wanna go back to windows, let's get this solved.
This issue is also on X11 but I would like to just use Wayland as everything is a lot better on there and feels smoother

Edit: also this effects me typing in my password and more than often I get locked out or my password doesn't work in terminal

SOLVED WITH COMMON SENSE: Turns out the problem was my own stupidity and ignorance to the fact it was not just on this computer, but on any of the few I tried... It's not an issue with arch it's an issue with me. I should have switched keyboards that was the first thing I should have tried, but I didn't.

WHAT I LEARNED: Don't be so ignorant 99% of the time it's not something super sophisticated and scary it's as simple as plugging in a new keyboard. Don't jump to the craziest conclusion, be ration-able.

Last edited by hlepme9 (2024-11-14 23:01:18)

V1del · 2024-11-14 12:28:54

you can configure the key repeat/delay setting to a higher value in system settings, have you tried that? Which keyboard? Do you see the same issue when checking the events you get while running

libinput debug-events

hlepme9 · 2024-11-14 12:41:03

I got very overwhelmed and I don't understand how to edit it correctly. I just want it to work as normal as if I was on Windows again. Steelseris Apex Pro TKL is the keyboard I use.

When I run that and hold tab it immediately releases..I did not let go of it.

event3 KEYBOARD_KEY +0.000s *** (-1) pressed
event3 KEYBOARD_KEY +0.167s *** (-1) released
event3 KEYBOARD_KEY +4.654s *** (-1) pressed
event3 KEYBOARD_KEY +4.938s *** (-1) released
event3 KEYBOARD_KEY +6.400s *** (-1) pressed
event3 KEYBOARD_KEY +6.507s *** (-1) released

V1del · 2024-11-14 13:07:49

Try disabling Rapid Trigger/increasing the actuation point: https://support.steelseries.com/hc/en-u … id-Trigger. -- stuff like this is probably configured in the driver on Windows and you'd have to use direct keyboard controls to dis-/enable such things on linux.

Last edited by V1del (2024-11-14 13:11:27)

hlepme9 · 2024-11-14 14:20:14

V1del wrote:

Try disabling Rapid Trigger/increasing the actuation point: https://support.steelseries.com/hc/en-u … id-Trigger. -- stuff like this is probably configured in the driver on Windows and you'd have to use direct keyboard controls to dis-/enable such things on linux.

You are a life saver you don't even understand. Thank you.

V1del · 2024-11-14 14:30:37

Nice, please mark as [SOLVED] by editing the title in your first post, maybe also add some info that it's a steelseries board so people running into similar issues have a reference point.

hlepme9 · 2024-11-14 16:12:09

V1del wrote:

Nice, please mark as [SOLVED] by editing the title in your first post, maybe also add some info that it's a steelseries board so people running into similar issues have a reference point.

Well I thought it was fixed... but it isn't... it seems to happen after using my computer for 30+ minutes. The only way I can temporarily get it to go away is if I delete my .config and .local how do I fix this permanently

seth · 2024-11-14 20:58:49

How does anything in your $HOME or even just the OS affect the keyboard internal rapid trigger status ?

The only way I can temporarily get it to go away

How "temporarily", do you just delete the config files or do you also reboot?
And

https://support.steelseries.com/hc/en-us/articles/18742108024717-How-to-activate-Rapid-Trigger wrote:

1. Press and hold the media button below the OLED screen.
2. Scroll using the OLED scroll wheel and select "Actuation" in the menu.
3. Click the scroll wheel to toggle Rapid Trigger on or off.
4. Press the media button twice to exit the OLED menu.
5. The number row lighting and OLED lightning icon will indicate the Rapid Trigger's status.

Does not work?
What is the current RT mode? Does it change when the problem emerges?

Sanity check: you mention windows a lot. Is there still a windows installation on that system?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

A possible issue could be https://wiki.archlinux.org/title/Power_ … utosuspend in case the keyboard gets suspended and resets w/ the reactivation.
Can you provoke this by leaving the keyboard alone for 10 minutes or so?

hlepme9 · 2024-11-14 21:53:24

seth wrote:

How does anything in your $HOME or even just the OS affect the keyboard internal rapid trigger status ?
The only way I can temporarily get it to go away
How "temporarily", do you just delete the config files or do you also reboot?
And
https://support.steelseries.com/hc/en-us/articles/18742108024717-How-to-activate-Rapid-Trigger wrote:
1. Press and hold the media button below the OLED screen.
2. Scroll using the OLED scroll wheel and select "Actuation" in the menu.
3. Click the scroll wheel to toggle Rapid Trigger on or off.
4. Press the media button twice to exit the OLED menu.
5. The number row lighting and OLED lightning icon will indicate the Rapid Trigger's status.
Does not work?
What is the current RT mode? Does it change when the problem emerges?
Sanity check: you mention windows a lot. Is there still a windows installation on that system?
3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.
A possible issue could be https://wiki.archlinux.org/title/Power_ … utosuspend in case the keyboard gets suspended and resets w/ the reactivation.
Can you provoke this by leaving the keyboard alone for 10 minutes or so?

I just meant it worked for a little bit after I did that. I'm going to try another keyboard.
RT Is off. I don't have the oled screen cause mine is %60 not the TKL I mistyped sorry. But I looked it up and it is off now. I had my pc off all night and now it's on and still doing it immediately. No windows install on the drive I formatted the entire thing twice.

seth · 2024-11-14 22:27:11

Please do not post pointless full quotes, you're just bloating the thread.

I just meant it worked for a little bit after I did that.

And does it work (again) if you repeat the process?
Also what exactly did you do if there's no OLED interface?
"SteelSeries key + T"?

And

RT Is off […]I looked it up and it is off now

how exactly do you do that?

I had my pc off all night and now it's on and still doing it immediately.

In case the configuration isn't stored in some nvram, you might have to rtoggle it off after every boot.

No windows install on the drive

The drive is irrelevant - do you run windows on that system at all?

Though

event3   KEYBOARD_KEY            +0.000s       *** (-1) pressed
event3   KEYBOARD_KEY            +0.167s       *** (-1) released
event3   KEYBOARD_KEY            +4.654s       *** (-1) pressed
event3   KEYBOARD_KEY            +4.938s       *** (-1) released
event3   KEYBOARD_KEY            +6.400s       *** (-1) pressed
event3   KEYBOARD_KEY            +6.507s       *** (-1) released

doesn't exaclty look like some rapid-trigger - there're 3 keyboard hits in 6.5s and the key is down for .17, .28 and .1 seconds - which is a very human performance level.
if it's not your finger, it's more likely a broken switch.
Can you test the keyboard on a differnet host (eg. a windows cmputer)?
Was there something like a CocaCola-incident?

hlepme9 · 2024-11-14 22:55:35

seth wrote:

Please do not post pointless full quotes, you're just bloating the thread.
I just meant it worked for a little bit after I did that.
And does it work (again) if you repeat the process?
Also what exactly did you do if there's no OLED interface?
"SteelSeries key + T"?
And
RT Is off […]I looked it up and it is off now
how exactly do you do that?
I had my pc off all night and now it's on and still doing it immediately.
In case the configuration isn't stored in some nvram, you might have to rtoggle it off after every boot.
No windows install on the drive
The drive is irrelevant - do you run windows on that system at all?
Though
event3   KEYBOARD_KEY            +0.000s       *** (-1) pressed
event3   KEYBOARD_KEY            +0.167s       *** (-1) released
event3   KEYBOARD_KEY            +4.654s       *** (-1) pressed
event3   KEYBOARD_KEY            +4.938s       *** (-1) released
event3   KEYBOARD_KEY            +6.400s       *** (-1) pressed
event3   KEYBOARD_KEY            +6.507s       *** (-1) released
doesn't exaclty look like some rapid-trigger - there're 3 keyboard hits in 6.5s and the key is down for .17, .28 and .1 seconds - which is a very human performance level.
if it's not your finger, it's more likely a broken switch.
Can you test the keyboard on a differnet host (eg. a windows cmputer)?
Was there something like a CocaCola-incident?

I'm trying something... a different keyboard. I have had water spills etc I don't know why that isn't the first thing that came to my mind, yes for some reason it is okay on other computers and on windows when I had it but you know... I never tried another keyboard, also I have had the same issue when installing arch on my old Laptop and using that keyboard... I feel so dumb for not noticing that haha. I do appreciate all of the help, maybe the fix is as simple as a different keyboard, writing this entire thing I did not have any issues at all so it's looking up from here.

Edit: Like I said I appreciate all of the help from @V1dal and @Seth. Can't believe I didn't try step one, another keyboard.

Last edited by hlepme9 (2024-11-14 23:02:16)

Arch Linux

#1 2024-11-14 12:11:33

[SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#2 2024-11-14 12:28:54

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#3 2024-11-14 12:41:03

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#4 2024-11-14 13:07:49

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#5 2024-11-14 14:20:14

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#6 2024-11-14 14:30:37

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#7 2024-11-14 16:12:09

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#8 2024-11-14 20:58:49

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#9 2024-11-14 21:53:24

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#10 2024-11-14 22:27:11

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

#11 2024-11-14 22:55:35

Re: [SOLVED (I WAS THE PROBLEM)] Keys are glitching :/

Board footer