[opensuse] Setting NumLock to On During logon
Hi, I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked. Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot. I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday, 6 July 2017 09:34:52 BST Koenraad Lelong wrote:
Hi,
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(.
Koenraad
If you are using Plasma, check systemsettings5/hardware/input devices, its configured there. I don;t know about other desktops but i guess its in a similar place. -- opensuse:tumbleweed:20170703 Qt: 5.9.0 KDE Frameworks: 5.34.0 KDE Plasma: 5.10.3 kwin 5.10.3 kmail2 5.5.2 akonadiserver 5.5.2 Kernel: 4.11.8-1-default Nouveau: 1.0.15_1.2 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 06-07-17 om 10:42 schreef ianseeks:
If you are using Plasma, check systemsettings5/hardware/input devices, its configured there. I don;t know about other desktops but i guess its in a similar place.
Hi, Indeed, I forgot the mention I'm running KDE. So I went to Systemsettings5/Hardware/input devices. There I did have : "no change" (I'm translating !) I changed it to "On" but the problem remains. Besides : that configuration seems for the user (I don't have to provide a root-password). So is this the right place ? Maybe of use (although see my last remark) : I installed from scratch on a "new" disk, but then I rsync'ed the /home partition. Thanks, Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong:
Op 06-07-17 om 10:42 schreef ianseeks:
If you are using Plasma, check systemsettings5/hardware/input devices, its configured there. I don;t know about other desktops but i guess its in a similar place.
Hi,
Indeed, I forgot the mention I'm running KDE. So I went to Systemsettings5/Hardware/input devices. There I did have : "no change" (I'm translating !) I changed it to "On" but the problem remains.
Besides : that configuration seems for the user (I don't have to provide a root-password). So is this the right place ?
Maybe of use (although see my last remark) : I installed from scratch on a "new" disk, but then I rsync'ed the /home partition.
Thanks, Koenraad
if i recall, i needed to reboot for it to work, did you do that? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-07-06 11:03, Koenraad Lelong wrote:
Op 06-07-17 om 10:42 schreef ianseeks:
If you are using Plasma, check systemsettings5/hardware/input devices, its configured there. I don;t know about other desktops but i guess its in a similar place.
Hi,
Indeed, I forgot the mention I'm running KDE. So I went to Systemsettings5/Hardware/input devices. There I did have : "no change" (I'm translating !) I changed it to "On" but the problem remains.
Besides : that configuration seems for the user (I don't have to provide a root-password). So is this the right place ?
Maybe if you do that for the user that runs the logon program. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
On July 6, 2017 1:34:52 AM PDT, Koenraad Lelong <k.lelong@ace-electronics.be> wrote:
Hi,
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was
running Linux at home. Now I'm having the same problem on Linux :-(.
Koenraad
Kde by chance? Kde has its own keyboard settings I believe. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op donderdag 6 juli 2017 10:34:52 CEST schreef Koenraad Lelong:
Hi,
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(.
Koenraad
This means you also moved from KDE4 to Plasma 5. Check systemsettings5 - input devices. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong:
Hi,
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(.
Koenraad
try going to configure desktop, then hardware configuration, there should be an option there for it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/07/17 10:34, Koenraad Lelong wrote:
Hi,
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(.
Koenraad
I've had this issue for a while running Leap 42.1 and 42.2 with Plasma. But, after forcing numlock to be ON in the sddm config file (that was the only way I could ensure it would work, none of the other Plasma or YaST settings did it for me) I find the LED is temperamental. Indeed, bizarrely, whilst reading your original post and this thread two minutes ago, I glanced down and noted the numlock LED was on, and now on typing this reply I see it is off. Yet numlock is always activated, it's just a problem of the LED. It is currently acting as a number pad if I type with it despite looking like it's set to off. I just checked whether I'd set the use of the LED to indicate when I'm on an alternate keyboard layout, I was sure I'd done that previously, but no, in Plasma System Settings there's nothing ticked there. So I just decided to reactivate that and choose scroll lock as the LED that indicates the change, and now when I press the key combo to change layout both the numlock and scroll lock light up. I change back again and scroll lock extinguishes but numlock stays active. So I'm really flummoxed as to what's going on there, it's a mess. gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong composed on 2017-07-06 10:34 (UTC+0200)
I switched from OS13.2 to Leap 42.2 a few days ago. Now I'm having the annoying problem that at logon I have to press numlock to enable the numbers-block on the keyboard of my laptop. In the BIOS the numlock is ON. When I boot, the numlock is on, also when grub is active. But after that, the numlock-led goes out, until I manually press the numlock button. In Yast/Hardware/systemkeyboard/advanced I did try to set the numlock to yes, but that didn't work. And it was set to BIOS, so it should have worked.
Am I missing something ? I read the thread of about a year ago, but that was about numlock at boot.
I hated it when Windows10 did that, and I considered myself lucky I was running Linux at home. Now I'm having the same problem on Linux :-(.
Try fixing it via /etc/sysconfig/keyboard: KBD_NUMLOCK="[yes,no,bios]" -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 06-07-17 om 11:21 schreef Felix Miata:
Try fixing it via /etc/sysconfig/keyboard:
KBD_NUMLOCK="[yes,no,bios]"
I tried that already, via Yast. But I did it anyway (set it to "yes", that is). No success. I have to say there is some progress though. I didn't see it before, because I enabled the numlock when I was at the logon-screen. Now I didn't touch the numlock key and I remarked that when the logon finished, the numlock was on. So it's only the logon-screen that's concerned. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong:
Op 06-07-17 om 11:21 schreef Felix Miata:
Try fixing it via /etc/sysconfig/keyboard:
KBD_NUMLOCK="[yes,no,bios]"
I tried that already, via Yast. But I did it anyway (set it to "yes", that is). No success.
I have to say there is some progress though. I didn't see it before, because I enabled the numlock when I was at the logon-screen. Now I didn't touch the numlock key and I remarked that when the logon finished, the numlock was on. So it's only the logon-screen that's concerned.
one last question, did you choose the type of keyboard in the dropdown menu on the gui? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Koenraad Lelong composed on 2017-07-06 11:45 (UTC+0200):
Felix Miata composed:
Try fixing it via /etc/sysconfig/keyboard:
KBD_NUMLOCK="[yes,no,bios]"
I tried that already, via Yast. But I did it anyway (set it to "yes", that is). No success.
I have to say there is some progress though. I didn't see it before, because I enabled the numlock when I was at the logon-screen. Now I didn't touch the numlock key and I remarked that when the logon finished, the numlock was on. So it's only the logon-screen that's concerned.
https://wiki.archlinux.org/index.php/SDDM#Numlock "If you want to enforce Numlock to be enabled, set Numlock=on in the [General] section." -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op 06-07-17 om 12:08 schreef Felix Miata:
https://wiki.archlinux.org/index.php/SDDM#Numlock
"If you want to enforce Numlock to be enabled, set Numlock=on in the [General] section."
Thanks, That seems to have done the trick. I made a new entry like on the website, now Nummlock is on at the logon-screen. Thanks all. Koenraad -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Carlos E. R. -
Felix Miata -
gumb -
ianseeks -
James Bunnell -
John Andersen -
Knurpht - Gertjan Lettink -
Koenraad Lelong