Bug 383962 - The Num Block key status isn't remembered between sessions
Summary: The Num Block key status isn't remembered between sessions
Status: RESOLVED DUPLICATE of bug 368063
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard (show other bugs)
Version: 5.10.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2017-08-24 16:38 UTC by Alberto Salvia Novella
Modified: 2020-08-11 16:59 UTC (History)
4 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 Alberto Salvia Novella 2017-08-24 16:38:27 UTC 
HOW TO REPRODUCE:
1. Turn the num block key on.
2. Reboot and log in again.

RESULT:
- The key is off, where it should be as in the last session.
- This small think forces you to think if the num block is turned on every time you use the numerical keyboard. Due to its frequency it's quite annoying.
Comment 1 Alberto Salvia Novella 2017-08-24 16:41:07 UTC 
Related bugs:
- NumLock doesn't follow BIOS setting (https://bugs.kde.org/show_bug.cgi?id=368063)
- Numblock doesn't follow settings (https://bugs.kde.org/show_bug.cgi?id=373646)
Comment 2 Thomas H 2017-08-24 18:56:55 UTC 
I found some discussion of this and a temporary workaround on this thread: https://forum.kde.org/viewtopic.php?f=289&t=133089

Add a "Numlock=on" string inside /etc/sddm.conf
Comment 3 Nate Graham 2017-11-29 03:27:11 UTC 

*** This bug has been marked as a duplicate of bug 368063 ***
Comment 4 Claudius Ellsel 2020-08-11 16:59:40 UTC 
(In reply to Alberto Salvia Novella from comment #1)
> Related bugs:
> - NumLock doesn't follow BIOS setting
> (https://bugs.kde.org/show_bug.cgi?id=368063)
> - Numblock doesn't follow settings
> (https://bugs.kde.org/show_bug.cgi?id=373646)

This should go to the "See Also" entry, not be list as dependency or blocker. Thus I removed both entries from there. They are already linked via the duplicate entry, so I am not adding them in "See Also".