You are not logged in.

#1 2025-08-23 17:32:27

GhostOverFlow256
Member
Registered: 2023-07-16
Posts: 11

Keyboard suddenly stopped working in GUI

Was playing a game, suddenly my keyboard stopped working entirely. From there, I hard restarted the computer by holding down the power button.

Upon reboot, I am able to login using the keyboard perfectly fine, but it stops working entirely once logged in to the desktop environment.
I am able to navigate in GRUB, bios, etc etc fine. If i swap TTY ***before*** logging in, I can type and log in fine.

If I run `sudo dmesg`, it returns: https://ghostoverflow.gay/xorg_logs.txt
Running `DISPLAY=:0 xinput`:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ HP, Inc HyperX Pulsefire Saga Pro       	id=13	[slave  pointer  (2)]
⎜   ↳ HP, Inc HyperX Pulsefire Saga Pro Keyboard	id=14	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Power Button                            	id=7	[slave  keyboard (3)]
    ↳ Cooler Master Technology Inc. MasterKeys Pro L White	id=8	[slave  keyboard (3)]
    ↳ Cooler Master Technology Inc. MasterKeys Pro L White System Control	id=9	[slave  keyboard (3)]
    ↳ Cooler Master Technology Inc. MasterKeys Pro L White Consumer Control	id=10	[slave  keyboard (3)]
    ↳ Cooler Master Technology Inc. MasterKeys Pro L White Keyboard	id=11	[slave  keyboard (3)]
    ↳ Blue Microphones Yeti Stereo Microphone Consumer Control	id=12	[slave  keyboard (3)]

I'm using gnome + xorg/x11 + lightdm as my greeter. Checking the xorg logs: https://ghostoverflow.gay/xorg_logs.txt
Running `journalctl -b | grep -i "crash\|segfault\|error" | grep -i gnome`: https://ghostoverflow.gay/journalctl_logs.txt

Offline

#2 2025-08-23 18:43:02

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,180

Re: Keyboard suddenly stopped working in GUI

Running `DISPLAY=:0 xinput`:

If i swap TTY ***before*** logging in, I can type and log in fine.

Is this before or after the login?
After the login, ctrl+alt+f3 does no longer work?
Can you ssh into the system and/or use a different keyboard?

Offline

#3 2025-08-23 20:26:08

GhostOverFlow256
Member
Registered: 2023-07-16
Posts: 11

Re: Keyboard suddenly stopped working in GUI

> Is this before or after the login?
Before any login to a desktop environment xinput does not work, as the x server has not started yet
```
$ DISPLAY=:0 xinput
Authorization required, but no authorization protocol specified

Unable to connect to X server
```
> After the login, ctrl+alt+f3 does no longer work?
Correct, no key inputs work at all, including those used for switching tty's.

> Can you ssh into the system and/or use a different keyboard?
SSH works perfectly fine, and I actually noticed something strange when attempting to use a different keyboard.

No matter what keyboard i use in the login screen, I can "tap" letters and they type fine. However, when I log in, I need to "hold" each key for ~1-1.5 seconds before it presses, and if i release early, it never submits the keypress.
Why this happens? NFI. Why it started in the middle of playing a game? NFI.

Offline

#4 2025-08-23 20:30:13

GhostOverFlow256
Member
Registered: 2023-07-16
Posts: 11

Re: Keyboard suddenly stopped working in GUI

Okay i think i figured it out? It may be a feature called "slow keys" that somehow got activated without telling me?
Disabling that seems to have fixed it, but I would appreciate any advice on how to make it so that it PERMANENTLY never enables again, as it seems that "press and hold Shift for eight seconds to enable or disable slow keys." is something that is not listed in the keyboard shortcuts.

Offline

#5 2025-08-23 20:37:45

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,180

Re: Keyboard suddenly stopped working in GUI

It may be a feature called "slow keys" that somehow got activated without telling me?

I was gonna say and ask you to check w/ https://aur.archlinux.org/packages/xkbset lol

https://help.gnome.org/users/gnome-help … ys.html.en

Offline

Board footer

Powered by FluxBB