[systemsettings] [Bug 368063] NumLock not 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 linn...@gmail.com changed: What|Removed |Added CC||linn...@gmail.com --- Comment #40 from linn...@gmail.com --- I have the same problem, that Numlock setting has no effect at all. Plasma version 5.20.4, X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 CC||yiz...@kulodgei.com --- Comment #46 from yiz...@kulodgei.com --- 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 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #47 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 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 Claudius Ellsel changed: What|Removed |Added Summary|NumLock not turned on |NumLock not is not turned ||on at start, although the ||preference for it is set to ||`on` in kcm_keyboard -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #28 from Claudius Ellsel --- Since this bug is (at least originally) about cases where the preference to always turn NumLock on is explicitly set, I created another one generally tracking the problem that this is not the default value: https://bugs.kde.org/show_bug.cgi?id=432107. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at Resolution|--- |REMIND Status|REPORTED|NEEDSINFO --- Comment #29 from Wolfgang Bauer --- (In reply to Greg Lepore from comment #22) > kreadconfig5 --file kcminputrc --group Keyboard --key NumLock > > produces a "0" That means "Don't change". But this bug report is about "NumLock not is not turned on at start, although the preference for it is set to `on`" So can anybody reproduce the problem when it is set to "on" in KDE/Plasma's settings? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #30 from Wolfgang Bauer --- (In reply to linus.kardell+kdebugs from comment #25) > I have the same issue on OpenSUSE Tumbleweed. The defaults for Tumbleweed are broken currently, see https://bugzilla.opensuse.org/show_bug.cgi?id=1179295. That's a downstream problem though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #31 from Greg Lepore --- Created attachment 135174 --> https://bugs.kde.org/attachment.cgi?id=135174&action=edit NumLock Settings -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #32 from Greg Lepore --- See attachment. NumLock is set to "Turn on" and kreadconfig5 --file kcminputrc --group Keyboard --key NumLock shows "0". These appear to be incompatible settings. I think my screenshot is accurately portraying the submitters report, isn't it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 Wolfgang Bauer changed: What|Removed |Added Ever confirmed|0 |1 Resolution|REMIND |--- Status|NEEDSINFO |REOPENED --- Comment #33 from Wolfgang Bauer --- (In reply to Greg Lepore from comment #32) > See attachment. NumLock is set to "Turn on" and kreadconfig5 --file > kcminputrc --group Keyboard --key NumLock shows "0". These appear to be > incompatible settings. > > I think my screenshot is accurately portraying the submitters report, isn't > it? Yes, I think it is. I just wanted to get rid of unrelated problems. Thanks for clarifying your case. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #34 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #33) > (In reply to Greg Lepore from comment #32) > > See attachment. NumLock is set to "Turn on" and kreadconfig5 --file > > kcminputrc --group Keyboard --key NumLock shows "0". These appear to be > > incompatible settings. > > > > I think my screenshot is accurately portraying the submitters report, isn't > > it? > Yes, I think it is. > > I just wanted to get rid of unrelated problems. > > Thanks for clarifying your case. Btw, is this X11 or Wayland, by chance? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #35 from Greg Lepore --- X11. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #36 from Claudius Ellsel --- (In reply to Greg Lepore from comment #32) > See attachment. NumLock is set to "Turn on" and kreadconfig5 --file > kcminputrc --group Keyboard --key NumLock shows "0". These appear to be > incompatible settings. > > I think my screenshot is accurately portraying the submitters report, isn't > it? Hm, I am not an expert, but it seems as if changes of this preference are not transferred correctly to the settings file? Out of curiosity, does the output of that command change if you change the preference in the settings? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #37 from Greg Lepore --- Yes, the settings change. Here is the mapping: Turn on = 0 Turn off = 1 Leave unchanged = 2 Which are different from Comment 29. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #38 from Wolfgang Bauer ---
(In reply to Greg Lepore from comment #37)
> Yes, the settings change. Here is the mapping:
>
> Turn on = 0
> Turn off = 1
> Leave unchanged = 2
>
> Which are different from Comment 29.
Yes, sorry, my mistake.
>From plasma-desktop/kcms/keyboard/kcmmisc.cpp:
enum TriState {
STATE_ON = 0,
STATE_OFF = 1,
STATE_UNCHANGED = 2,
};
So the problem is apparently *not* that the setting is not saved correctly.
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #39 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #38) > From plasma-desktop/kcms/keyboard/kcmmisc.cpp: It's kcmmisc.h of course. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #45 from linn...@gmail.com --- I have this problem again, after reinstall Linux. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #44 from linn...@gmail.com --- I have ibus installed. But, now the Numlock setting WORKs again (really strange, I did not do anything unusual) - that I even forgot that I had this bug. (In reply to Wolfgang Bauer from comment #42) > I have another idea though: > I do remember bug reports where ibus interfered with KDE's keyboard settings. > I have no idea whether it also changes the NumLock state, but maybe that > would be a possible reason? > > I.e. do you have ibus installed? > And does it help to uninstall it? (ibus itself, libibus shouldn't matter) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 Ninguém changed: What|Removed |Added CC||lv215...@anonaddy.me --- Comment #41 from Ninguém --- I have this problem in a intermittent way in 5.21.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #42 from Wolfgang Bauer --- (In reply to linnets from comment #40) > I have the same problem, that Numlock setting has no effect at all. > Plasma version 5.20.4, X11. Well, it does work fine here. I have another idea though: I do remember bug reports where ibus interfered with KDE's keyboard settings. I have no idea whether it also changes the NumLock state, but maybe that would be a possible reason? I.e. do you have ibus installed? And does it help to uninstall it? (ibus itself, libibus shouldn't matter) (In reply to Ninguém from comment #41) > I have this problem in a intermittent way in 5.21.4 What exactly does "intermittent way" mean? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 368063] NumLock not 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 #43 from linus.kardell+kdeb...@gmail.com --- I had ibus, but removing it doesn't help -- You are receiving this mail because: You are watching all bug changes.
