Bug 500827 - Keyboard Indicator applet does not provide the correct information when Num Lock is active
Summary: Keyboard Indicator applet does not provide the correct information when Num L...
Status: RESOLVED DUPLICATE of bug 501159
Alias: None
Product: kdeplasma-addons
Classification: Plasma
Component: Keyboard Indicator (show other bugs)
Version: 6.3.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-27 18:12 UTC by pafrape
Modified: 2025-03-07 18:22 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pafrape 2025-02-27 18:12:52 UTC 
SUMMARY

The component does not display the correct information:
- when selecting only "caps lock", it indicates nothing.
- when selecting only "num lock", it also indicates when caps lock is activated although this should only indicate num lock.
- when selecting only "capslock" and "num lock", it is correct.


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Archlinux
KDE Plasma Version: 6.3.2
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Comment 1 TraceyC 2025-02-27 21:15:37 UTC 
I'm not able to readily reproduce this on Plasma 6.3.2 or built from git-master, hopefully someone else can
Comment 2 Nate Graham 2025-02-28 17:30:49 UTC 
I also can't reproduce this.

Do you by any chance have your caps lock key re-bound to do something else?
Comment 3 pafrape 2025-03-02 20:36:49 UTC 
The problem is only when selecting only "num lock" :
- it indicates num lock when num lock is activated and caps lock is inactivated ; It is normal.
- it indicates nothing when num lock is activated and caps lock is activated, whereas it should indicates num lock.
Comment 4 Nate Graham 2025-03-04 15:59:00 UTC 
Unfortunately I don't have a keyboard with a Num Lock key to test this with. I'll leave it open so someone else with appropriate hardware can have a go.
Comment 5 pafrape 2025-03-05 11:42:54 UTC 
I tried on Fedora, and the problem is exactly the same.
Comment 6 Nate Graham 2025-03-07 18:22:50 UTC 
*** This bug has been marked as a duplicate of bug 501159 ***