Summary: | NumLock settings are not being applied | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | clivejo <clivejo> |
Component: | kcm_keyboard | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | claudius.ellsel, greg, sabayon11, tuxfusion |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
clivejo
2017-12-22 16:28:03 UTC
I'm also seeing this bug on Neon. KDE Frameworks 5.41.0 Qt 5.9.3 (built against 5.9.3) Linux lepore-desktop 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Same here. BIOS enables it. During systemd boot messages it turns off. It is set to be enabled in systemsettings, but will not be enabled by KDE Arch Linux qt: qt5-base 5.10.1 Linux: 4.15.15-1-ARCH plasma-framework 5.44.0 plasma-workspace 5.12.4 systemsettings 5.12.4 sddm 0.17.0 I have it on Manjaro, Plasma 5.13.4 qt 5.11.1 Framework 5.48.0 4.14.65-1-MANJARO #1 SMP PREEMPT Sat Aug 18 13:29:56 UTC 2018 x86_64 GNU/Linux This may be related to SDDM bugs. https://github.com/sddm/sddm/issues/508 I think it would be best if this option in Plasma could be independent of other system components. Most people advise to change option is SDDM config file but this didn't work for me. This works for me: https://forum.manjaro.org/t/solved-how-to-turn-on-numlock-on-boot-on-plasma/8301/8 Create a file named in /etc/xdg/autostart. Using a text editor, put this in the file: cat numlockx-on.desktop [Desktop Entry] Type=Application Name=Numlock on Exec=numlockx on NoDisplay=true OnlyShowIn=KDE Name[en_US]=numlockx-on Sorry. Obviously file name must be numlockx-on.desktop and must be located in /etc/xdg/autostart With the following content: [Desktop Entry] Type=Application Name=Numlock on Exec=numlockx on NoDisplay=true OnlyShowIn=KDE Name[en_US]=numlockx-on *** This bug has been marked as a duplicate of bug 368063 *** |