What happens: Ctrl sticky key will not unstick
Reproducible steps:
1. Edit a file with nano
2. Save the file with Ctrl o
3. Press Enter to confirm save (without deselecting Ctrl)
4. Ctrl button is now stuck and require closing and restarting Terminal
Edit: Just tried unselecting Ctrl prior to pressing Enter to confirm the save and had the same result, so it appears to occur always after saving with nano
this is no longer an issue since we have switched to osk stub.
Sven 30/01/2025 5:38 pm
@fakeshell How do I ensure that the correct keyboard is running? I only see /usr/libexec/gsd-keyboard in pstree on my updated device.
fakeshell 30/01/2025 6:51 pm
you can do
ps aux | grep squeekboard
ps aux | grep phosh-osk-stub
phosh-osk-stub should be running
With gnome-console 46.0-2, I cannot reproduce your problem. I tried nano and emacs -nw.
Last night I was regularly triggering it while messing with udev rules and blacklisting modules, of course today I got it to trigger once but not again with screen recording turned on.
Ah just gave it one more try and got it! Posting shortly. Also new thing I learned is switching windows unsticks the sticky key without having to full close.
I take it back, it wont let me upload.
Exact steps I took:
cd /etc/udev/
cd rules.d/
sudo nano 10-rtl-sdr.rules
(entered sudo password)
wrote in file
Ctrl -O
Enter
(ctrl still engaged) x
...and stuck
Switching Console Tabs (to turn off wf-recorder) disabled it being stuck. The screen recording seems to just sit there because the keypress flash doesn't show with it being stuck.
This sounds like this old upstream bug which not solved yet.
https://gitlab.gnome.org/World/Phosh/squeekboard/-/issues/370
Edit. Link seems unvisible but "It seems that the state of the modifier keys cannot be disabled when squeekboard shows a different keyboard page than the one the modifier key had been enabled in."
Thanks for that info.
I am just glad I found a workaround by pressing new terminal tab (then going back into the same terminal tab). It was quite annoying to have to close the terminal then reopen and restart what I was doing
In my opinion you are mistaken. I suggest it to discuss. Write to me in PM.
