Description of problem: Each time I reboot the num-lock functionality is always off even though I activate it in system settings Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Set Num-lock on in system settings under Input devices | Keyboard 2. Reboot 3. Open e.g. konsole and press any number e.g. 8 key in numerical keyboard. Instead of entering the number the underlying arrow control is activated I have to manually activate num- lock 4. Do the same with the others options in Input devices | keyboard
Source RPM: (none) => plasma-desktop-5.20.4-1.mga8.src.rpmAssignee: bugsquad => kde
Summary: Num-lock is always off => Num-lock is always off when logging into Plasma
With a multi-desktop up-to-date Mageia 8 system, SDDM -> Plasma, I do not see this. NumLock is on, and in my experience of M8 always has been. No configuration of it manually. Looking in System Settings-Hardware-Input Devices-Keyboard-Numlock on Plasma Startup, I see it is set to 'leave as is'. (In the past, it *was* often necessary to activate it manually). Please try that option. You should not I think have to configure it. To see something of your system, if you do not yet have 'inxi' (it will soon be standard), please install it and post the O/P of: $ inxi -SMxx Also, please say how you installed Mageia 8, and what desktops you have. > I have to manually activate num-lock One touch, a light...
Severity: normal => minorCC: (none) => lewyssmith
I did a standard installation of mga8b2 with plasma. No special choices. But from first try I got this irritating behaviour that I have to active NumLock. Therefore I started investigating three options. Of course I have inxi installed. The report is attached
Created attachment 12194 [details] Output from inxi -SMxx
Thank for for this info. (It was small enough to post directly). > Of course I have inxi installed We have only just made it installed by default. Another simple question: when you boot, and see the login (display manager = SDDM ?) screen, is numlock off at that point? On my own system, it is on from the start - even when using SDDM. Would you be willing to install another display manager (say xddm or lightdm) to compare behaviour? I cannot do this for you because I do not see the problem.
Another thing to do, rather than try, please: $ journalctl -b --no-hostname | grep numlock Mine shows: Ion 10 19:45:10 numlock[689]: Cychwyn numlock:[ Iawn ] *** Ion 10 19:45:10 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=numlock comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' *** Start numlock: [ OK ]
In order to have Numlock feature in SDDM, user must add: Numlock=On in /etc/sddm.conf as root. There is no GUI support currently for this. Request it at https://github.com/KDE/sddm-kcm This will be permanent. Under a tty: install numlock Important: it is deactivated for laptop. do as root : # systemctl enable numlock Under Plasma, systemsettings5 => Input Devices => keyboard => Make sure it is set to a 105 key keyboard type as by default it is set to 86. Bug here? Then, right under, set it to "Turn On" instead of "Leave unchanged". If this is still inoperative, please report back.
CC: (none) => ouaurelienSource RPM: plasma-desktop-5.20.4-1.mga8.src.rpm => plasma-workspace-5.20.4-3.mga8.src.rpm
Note that upstream, this is reported and confirmed. The workaround is to activate it in sddm. https://bugs.kde.org/show_bug.cgi?id=368063 Also filled a request to have a GUI toggle in sddm-kcm (The Systemsettings module to configure sddm) https://bugs.kde.org/show_bug.cgi?id=431405
URL: (none) => https://bugs.kde.org/show_bug.cgi?id=368063
(In reply to Aurelien Oudelet from comment #6) Thanks for all the expert advice. > In order to have Numlock feature in SDDM, user must add: > Numlock=On > in /etc/sddm.conf Curious; on my box: $ grep Numlock /etc/sddm.conf #Numlock= $ > install numlock Astonished that it might not be; I would never have thought of that! Could have asked at the beginning for: $ rpm -q numlock @Hans : can you check whether it *was* installed? > Important: it is deactivated for laptop Important to know; here, Hans' system says it is a Desktop.
(In reply to Lewis Smith from comment #8) > (In reply to Aurelien Oudelet from comment #6) > Thanks for all the expert advice. > > In order to have Numlock feature in SDDM, user must add: > > Numlock=On > > in /etc/sddm.conf > Curious; on my box: > $ grep Numlock /etc/sddm.conf > #Numlock= > $ > > > install numlock > Astonished that it might not be; I would never have thought of that! Could > have asked at the beginning for: > $ rpm -q numlock > @Hans : can you check whether it *was* installed? > > > Important: it is deactivated for laptop > Important to know; here, Hans' system says it is a Desktop. Numlock will never be installed by default because it has know issues with laptop keyboards. User must by choice try to use it in such systems. Also, for same reasons it not activated by default in sddm.
@Lewis Smith Q: Another simple question: when you boot, and see the login (display manager = SDDM ?) screen, is numlock off at that point? On my own system, it is on from the start - even when using SDDM. A: Numlock is already off at login To the other questions.I have: $ rpm -q numlock The package numlock is not installed $cat /etc/sddm.conf InputMethod= [Users] HideShells=/sbin/nologin,/bin/false,/usr/sbin/nologin,/bin/true HideUsers=mysql,apache,mldonkey RememberLastUser=true [Autologin] User=hansmicheelsen Session=01plasma.desktop $journalctl -b --no-hostname | grep numlock
>> install numlock > Astonished that it might not be; I would never have thought of that! I suppose it is because I am old enough to remember DOS... I can add nothing useful to this. I see the point about Numlock being problematic with short laptop keyboards. I wonder if the installer can tell the difference (inxi apparently can); and if so, install & activate it for Desktop PCs. Or use the keyboard size as a clue. What do you think? If then it is started before login, whatever SDDM thinks should not matter.
Since plasma 5.20 there is a new method to activate the numlock , you have to: 1. Set Num-lock to "Turn on" in systemsettings under Input devices | Keyboard 2. Go to Startup and Shutdown -> Login Screen (SDDM) -> Advanced 3. Settings synchronization click now to the "Sync" button. 4. reboot
CC: (none) => geiger.david68210
I tried that after uninstalling numlock. I couldn't get it to work. I tried all sorts of combinations of turning on numlock in settings, on the keyboard, applying "sync" before and after. I even tried to the "reset" button before "sync". Luckily it didn't reset any other settings. I really think this issue should be solved before releasing Mga 8. Its kind of awkward to have to install an additional program for numlock. I don't think the average user would appreciate that solution.
I encountered this issue but after doing what I said in comment 12 now all is fine! We can't do more!
Created attachment 12254 [details] Showing SDDM Numlock options in its config editor What about 'sddm-config-editor' (which you have to install; should it be included with SDDM?). Does that work?
CC: lewyssmith => (none)
Another thought. $ rpm -q numlock numlock-2.1.2-15.mga8 My system journal shows: $ journalctl -b | grep numlock Ion 24 19:58:06 localhost.localdomain numlock[682]: Cychwyn numlock:[ Iawn ] = Starting numlock:[ OK ] @Hans: Assuming numlock is installed (another package that should always be), can you please look in the journal for it?
I get: # rpm -q numlock numlock-2.1.2-15.mga8 # journalctl -b | grep numlock jan 24 22:01:12 localhost.localdomain numlock[942]: Starter numlock: [ O.k. ]
I have installed sddm-config-editor and notiched the text beneath Initial Numlock state.Can be on, off or none. The message says:If property is et to none, numlock wont be changed. NOTE: Currently ignored if autologin is enabled. I have autologin enabled. I'll see if works with autologin disabled.
(In reply to David GEIGER from comment #14) > I encountered this issue but after doing what I said in comment 12 now all > is fine! > > We can't do more! (In reply to Hans Micheelsen from comment #18) > I have installed sddm-config-editor and notiched the text beneath Initial > Numlock state.Can be on, off or none. > The message says:If property is et to none, numlock wont be changed. > NOTE: Currently ignored if autologin is enabled. > I have autologin enabled. I'll see if works with autologin disabled. Users who have experienced this problem are encouraged to follow these steps: Since plasma 5.20 there is a new method to activate the numlock , you have to: 1. Make sure you have a 100/102/104/105-key keyboard in systemsettings under Input devices | Keyboard. 2. There, set Num-lock to "Turn on". 3. Go to Startup and Shutdown -> Login Screen (SDDM) -> Advanced 4. Settings synchronization click now to the "Sync" button. 5. Reboot Upstream can make silly default choices but the main issue is to activate or not numlock on *ALL* hardware. There are numpad on some *laptop* keyboards that are on alphabetical keys. So, numlock can't be activated by default on such hardware because we will have complains about keys that display "789" instead of "uio" for e.g.. Also, x11keymap can't recognize properly the size of such keyboards. User must configure his keyboard size in systemsettings. As this is rather an upstream bug, https://bugs.kde.org/show_bug.cgi?id=368063 AND there is simple workaround, leaving this open.
Source RPM: plasma-workspace-5.20.4-3.mga8.src.rpm => plasma-workspace-5.21.5-1.mga9.src.rpmStatus: NEW => UPSTREAMAssignee: kde => ouaurelienTarget Milestone: --- => Mageia 9
I'm seeing this in MGA8 Plasma on my HP Probook 6550b with a 101-key keyboard, but not on any of my desktops, all of which use Logitech wireless 104(?)-key keyboards. It continues to happen, even after applying the workaround in Comment 19. It did not happen with Mageia 7. This laptop has an LED numlock indicator. During the boot, I can watch the LED come on for Grub2, then off, then on again later, then off again, to stay off. Interestingly enough, when numlock is off, those keys don't have their alternative functions - they are just disabled. Yes, it is annoying, but unfortunately it is far from the most annoying thing I must endure in my life, so I will just have to put up with it.
CC: (none) => andrewsfarm
CC: (none) => doktor5000