[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #52 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Grete Mueller changed: What|Removed |Added Version|5.26.3 |5.27.9 CC||knoblauchla...@alphafrau.de Status|RESOLVED|REOPENED Resolution|FIXED |--- Platform|Kubuntu |Debian testing --- Comment #58 from Grete Mueller --- >kreadconfig5 --file kcminputrc --group Keyboard --key NumLock >0 >echo $XDG_SESSION_TYPE >x11 >ps -A |grep kglobalaccel >1229 ?00:00:00 kglobalaccel5 Nothing helped except: >apt install numlockx -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #59 from Nate Graham --- This is a fairly old bug report and the code has changed a lot since it was reported. There's a very good chance the issue you're experiencing is caused by something else, even if the outward symptoms look and feel the same. Can you please submit a new bug report? Thank you! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #53 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 cartes changed: What|Removed |Added CC||carte...@aliceadsl.fr -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 denni...@selectedovr.com changed: What|Removed |Added CC||denni...@selectedovr.com --- Comment #49 from denni...@selectedovr.com --- Is this being worked on? It is driving me crazy. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=454478 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 yiz...@kulodgei.com changed: What|Removed |Added Summary|NumLock not is not turned |NumLock is not turned on at |on at start, although the |start, although the |preference for it is set to |preference for it is set to |`on` in kcm_keyboard|`on` in kcm_keyboard -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #48 from yiz...@kulodgei.com --- (In reply to yizel7 from comment #46) > This is an issue for my laptop. I have the correct Keyboard model selected > from the dropdown menu (Acer | Acer laptop) and then in the NumLock on > Plasma Startup The "Turn on" radio button is selected. When I restart the > NumLock key is NOT on. I have to manually toggle the NumLock key on my > keyboard to turn it on. This is not the expected behavior. > > SOFTWARE/OS VERSIONS > OS: Arch Linux x86_64 > Kernel: 5.14.12-arch1-1 > (available in About System) > KDE Plasma Version: 5.23.1 > KDE Frameworks Version: 5.87.0 > Qt Version: 5.15.2 I now have an external keyboard plugged into my laptop and the situation is the same. NumLock is not on when I turn on my computer even though it is set to be turned on in System Settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Martin changed: What|Removed |Added CC||spleefe...@gmail.com --- Comment #60 from Martin --- (this thread is linked in other places) New bug report can be found here - https://bugs.kde.org/show_bug.cgi?id=485940 Adjacent bug report is also here (on=on but last-state==on=off) - https://bugs.kde.org/show_bug.cgi?id=454478 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 deemon changed: What|Removed |Added CC|pr...@ww.ee | -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Titouan Camus changed: What|Removed |Added CC||szots...@gmail.com --- Comment #61 from Titouan Camus --- *** Bug 485940 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #62 from Szőts Ákos --- This is a 2016 bug which was marked as fixed on an unspecified date. 485940, which was marked as a duplicate of this, is fairly new. In order not to close a valid bug as "fixed", "duplicate", may I ask when was this bug fixed? If you take a look at 485940, multiple people are still bumping into this issue in 6.0.4. If you think 485940 is a still valid and new bug, please, reopen it as such. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Conor Campbell changed: What|Removed |Added Resolution|FIXED |--- CC||co...@bromedia.co.za Status|RESOLVED|REOPENED --- Comment #63 from Conor Campbell --- A fix which worked for me: sudo nano /usr/lib/sddm/sddm.conf.d/default.conf Numlock=on I think the reason it is broken, is because the default setting is Numlock=none, and the src/greeter/GreeterApp.cpp file in SDDM doesn't have a case for Numlock=none. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #64 from Conor Campbell --- (In reply to Conor Campbell from comment #63) > A fix which worked for me: > > sudo nano /usr/lib/sddm/sddm.conf.d/default.conf > > Numlock=on > > I think the reason it is broken, is because the default setting is > Numlock=none, and the src/greeter/GreeterApp.cpp file in SDDM doesn't have a > case for Numlock=none. In fact, even creating /etc/sddm.conf.d/numlock.conf and adding Numlock=on works, it seems. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Christian Hartmann changed: What|Removed |Added CC||hartmann.christ...@gmail.co ||m --- Comment #57 from Christian Hartmann --- just to reensure, that the daemon not started is the issue here. this numlock issue drove me nuts since three month or so. other isssue: i've disabled key repeating on longer press and this also didn't work as exspected. since i've started the daemon manualy also this feature is going .. i'm quite confident in saying: i've never ever changed the behavior of this autostart setting. i've actualy didn't know about this one to the day. (running neon) closing words: i do not feel very comfortabel with a setting, where 0 (zero) is for *en*abling something. same with "do not change setting" just deletes the whole NumLock line in kcminputrc. if one never touched the setting, no line in the rc file feels right, but the moment, the user *does* set the behavior this explicit setting should reflect in a file. just my 2ct, sorry -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Nate Graham changed: What|Removed |Added Priority|VHI |HI -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 TraceyC changed: What|Removed |Added CC||guido-kdebugs@unknownsite.d ||e --- Comment #65 from TraceyC --- *** Bug 477374 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 ezh changed: What|Removed |Added CC||eugene.savit...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #66 from ezh --- Just filled a bug: https://bugs.kde.org/show_bug.cgi?id=487638 Changing NumLock to ON in Keyboard Settings should also change it or offer to change for SDDM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #67 from ezh --- Created attachment 169884 --> https://bugs.kde.org/attachment.cgi?id=169884&action=edit Where to apply the NumLock for SDDM You have to apply the NumLock setting for SDDM (login screen) in a way different place. That should be changed. See screenshot from bug 487638. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 fanzhuyi...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=487638 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #68 from fanzhuyi...@gmail.com --- *** Bug 485940 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 fanzhuyi...@gmail.com changed: What|Removed |Added Version|5.27.9 |6.0.4 CC||fanzhuyi...@gmail.com Status|REOPENED|CONFIRMED --- Comment #69 from fanzhuyi...@gmail.com --- Confirming from number of duplicates, and bumping version to 6.0.4, which most recent duplicates are reported against -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 fanzhuyi...@gmail.com changed: What|Removed |Added CC||gtx.sw...@gmail.com --- Comment #70 from fanzhuyi...@gmail.com --- *** Bug 491346 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 KaKi87 changed: What|Removed |Added CC||kak...@proton.me --- Comment #71 from KaKi87 --- Hi, I'm sorry I can't figure out how to just subscribe to updates for this issue so I'm commenting in order to get subscribed. Thanks -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED Priority|NOR |VHI --- Comment #50 from Nate Graham --- Raising priority due to number of duplicates. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Fabian Vogt changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #51 from Fabian Vogt --- Assuming that "numlockx off/on" works, but "kded5 --replace" does not: - Is "keyboard daemon" enabled in "background services"? - What's the output of "gdb -ex 'break XkbLockModifiers' -ex r -ex bt -ex quit --args kded5 --replace"? - What's the output of "gdb -ex 'break KModifierKeyInfo::setKeyLocked' -ex r -ex bt -ex quit --args kded5 --replace"? (Answer "yes" if gdb asks something) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 tomas nackaerts changed: What|Removed |Added Resolution|WORKSFORME |--- CC||tomas.nackae...@gmail.com Status|RESOLVED|REOPENED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 tomas nackaerts changed: What|Removed |Added Version|5.5.5 |5.26.3 --- Comment #54 from tomas nackaerts --- Remember having this problem years ago, went away but can't remember why. Started happening again a few weeks ago. Currently using plasma 5.26.3 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 --- Comment #55 from tomas nackaerts --- (In reply to Fabian Vogt from comment #51) > Assuming that "numlockx off/on" works, but "kded5 --replace" does not: > - Is "keyboard daemon" enabled in "background services"? > - What's the output of "gdb -ex 'break XkbLockModifiers' -ex r -ex bt -ex > quit --args kded5 --replace"? > - What's the output of "gdb -ex 'break KModifierKeyInfo::setKeyLocked' -ex r > -ex bt -ex quit --args kded5 --replace"? > > (Answer "yes" if gdb asks something) Didn't see this comment when i reopened this bug report. Seems like the keyboard daemon was for some reason not running. after starting the daemon the numlock turned on. I will check in the following days if this permanently fixes this issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock is not turned on at start, although the preference for it is set to `on` in kcm_keyboard
https://bugs.kde.org/show_bug.cgi?id=368063 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #56 from Nate Graham --- It should. If you have reason to suspect that the daemon not being running automatically is a bug, please open a new bug report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
