For decades up until a very recent update, the CAPS LOCK only changed the capitalization of letters, and didn’t affect other keys.
In a recent update, this seems to have changed. It does that, but it also breaks the backspace key so it doesn’t work at all, arrow key will start selecting areas instead of just moving the cursor in programs like Kate…
I want the previous normal CAPS LOCK behavior back.
I’ve found the “Caps Lock Behavior” entry in Keyboard → Key Bindings, but for the life of me I can’t find an entry that just does what CAPS LOCK used to do.
I want it to just affect capitalization of letters, and leave my backspace and other keys alone. Like it used to. Is this still possible?
Nah… personally I reset the CapsLock to be my Compose key, so now when I hit that key, Caps Lock helps me type pointers or thumbs , ticks or even Thai phrases (ขอบคุณมากครับ เจอกันใหม่ครั้งหน้าครับ = ‘tvm’).
For caps (as we don’t usually type many) I use Shift, and L_ShiftR_SHIFT together does Shift Lock (useful for passwords).
CAPS LOCKED 123
SHIFT LOCKED !@#
Yup, all working fine.
Settings should all be clear in the Keyboard settings module.
Hi! To help folks best guide you, could you please provide your basic system information from the Info Center app? The Copy Details button is the easiest way to get that ready to paste in:
Related to this issue - when it occurs, are all keys acting as if Shift is being held - ex. numbers are typing the corresponding symbols, etc.?
And, if you go to a virtual console using Ctrl+Alt+F3 and login, does that issue persist there? Trying to figure out whether or not the issue could sit within the desktop environment somewhere, or if it is happening somewhere between your hardware and the kernel itself
Unchecking it doesn’t change the issue.
And it’s the same layout prior to the update that somehow changed this. I’m not changing to a layout that doesn’t work over it.
Eh… the average user doesn’t do things like virtual consoles, so please don’t be suggesting people do that without telling them how to get out of it when done. I was expecting a window to open, not my desktop to be taken over, and there was no clue how to exit it. Fortunately I didn’t lose any work.
But no. It’s only happening within QT-based programs, like Kate and LibreOffice. It’s fine in Firefox, Gimp, and various GTK programs.
There’s no problem when typing in Konsole (bash), either.
When this occurs, it capitalizes letters as normal. The numbers are fine, they are “unshifted”. But the Backspace stops working, the Enter stops working, and arrow keys will move but start highlighting things instead of just moving the cursor (when working in text in Kate for example).
I’ve been using KDE since the 2.x days, and I’ve never had this happen before.
Operating System: openSUSE Tumbleweed 20250501
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.9.0
Kernel Version: 6.14.4-1-default (64-bit)
Graphics Platform: X11
Processors: 8 × 13th Gen Intel® Core™ i3-13100F
Memory: 15.5 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1660 SUPER
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D96
System Version: 2.0
Lolz I can’t disagree with this… only a few years ago, things that were easily discovered or understood by most people are way beyond the intelligence of even ‘seasoned’ users of the desktop.
Even knowing you can switch between consoles with CtrlAltF1-F6…
It’s hard to imagine that someone wouldn’t try different F keys to find their original console… I remember that it can be different on different systems too, on my Desktop the default is TTY4, but it can be different.
It is very common for people to rely on the aspect of common knowledge - and the person giving you advice considers this an extremely basic skill…
However, the next most basic skill I would suggest from anyone using KDE Plasma is the ability to completely circumnavigate settings and test whether their basic system is sound.
From this position, I would begin by doing this:
mv .config .configBORKED
Then log out and in again, and see if the issue persists. It’s highly likely the ‘bug’ is in your .config folder somewhere.
or thumbs 
, ticks 
or even Thai phrases (ขอบคุณมากครับ เจอกันใหม่ครั้งหน้าครับ = ‘tvm’).
