HP Laptop Keyboard

[GreyGeek]

I never use the numeric keypad to enter numbers so I never tested the numlock key. I have Debian Bookworm installed on this two year old HP-17c1xxx* laptop and I found that the numlock key works fine when I am testing it in a Kate text file. I just tested it in this post and it worked as it should.

[raimund]

Hey,

i tried to aktivate the "numlock" after installation of fresh Kubuntu
23.10 on two Notebooks and two Virtual Machine.
3 times with german language and 1 time with english language.



Every time it doesn`t was succesfully.

The control-light was on, but the numlock keys do not work.

The problem is that the config-file
"/etc/sddm.conf.d/kde_settingsconf" wasn't automaticly created.

I can solve this problem if do "Apply Plasma Setting.." in "System
Settings -> LoginScreen (SDDM)"


With friednly regards

Raimund ERNST

[Oderus]

Both of these issues have been confirmed as bugs. Thanks everyone.

[Oderus]

Not that it helps, but here I set numlock on in both sddm and plasma as I described above and it works every time. I also have "Leave unchanged" set in System settings. Point being that it could be an issue specific to 23.04 and/or the kernel you're using.

Did you have 22.04 on either of these machines prior to 23.04? Just curious if this behavior is new or if you've seen it before.

I did, I had 22.04 on my desktop PC and it worked just fine.

[oshunluvr]

Not that it helps, but here I set numlock on in both sddm and plasma as I described above and it works every time. I also have "Leave unchanged" set in System settings. Point being that it could be an issue specific to 23.04 and/or the kernel you're using.

Did you have 22.04 on either of these machines prior to 23.04? Just curious if this behavior is new or if you've seen it before.

[Oderus]

Still having problems with both of these things. SDDM requires (despite configuration, numlockx, etc) numlock to be pressed twice to actually come on. Also, i have tried every kernel module i can think of to try and get my mute button LED to work, and have had zero luck.

[Oderus]

Alright something is legit wrong with it. My other PC, a very old desktop, which has always worked with numlock in sddm, also is doing the same exact thing (after updating). I have to press numlock twice to get numlock to be active.

[GreyGeek]

I am running an 18 month old HP-17cn1*** laptop with LED illuminated keypads. In the BIOS I turned the lights on for the max allowed time.
After about 30 seconds of not touching the keyboard the lights go out. If I touch the space bar the come on. Or, I can touch and hold the F4 key to turn on and brighten the lights from off to max.

[Oderus]

Bit of an update, i tried enabling several different things in modprobe.d/alsa-base.conf, abseloutely no luck at all. By searching around it seems people have had this exact issue for years with realtek alc236. What a shame it's never been implemented. Is there anything else i can do to possibly fix this or report it to the appropriate person to be implemented?

Also, i tried a few ways to get numlock to come on before sddm, as i'd like it on when sddm pops, but no luck. as a matter of fact I have to press numlock twice on sddm to get it to come on

[Oderus]

Unfortunately I couldn't even get xset to turn on and LED that does work (caps lock). Does turn on when i press it though.

The LEDs may be just not supported by the kernel. you can try "xset" to manually switch them on or off to see if they work.

[oshunluvr]

The LEDs may be just not supported by the kernel. you can try "xset" to manually switch them on or off to see if they work.

[Oderus]

I tried deleting the cache and rebboting, but had no luck with that. I will check out the link you supplied above and see if that helps. Thank you. The make is HP Laptop 15-ef0xxx.

You are welcome.

What is the exact name/model number/type of your HP laptop?

Numlock=on in an sddm configuration file sets NumLock for sddm only.

Here are some general possibilities for "activating NumLock on bootup": https://wiki.archlinux.org/title/Act...lock_on_bootup

This could also be too general of an idea, but did you try erasing your user's caches, logging out and in again after this and then trying the System Settings again?:
Best done from another user account or a tty: sudo rm -r /home/your_user_name/.cache/*

[Oderus]

Not sure if you're just making typos - but it's numlock not numblock

sddm.conf should contain something like:

[Autologin]
Session=plasma
​
[General]
Numlock=on

From what I've read you have to have both sddm,conf and plasma set to numlock=on

As far as the LED, possibly a boot setting could fix that but you didn't tell us the model of HP.

Hmmmm yes I did make a mistake there in the message, i do have Numlock=on under General, and have it set to on in settings as well. I do apologize for not supplying the make of the pc, which is :

Operating System: Kubuntu 23.04
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.2.0-20-generic (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
Memory: 13.6 GiB of RAM
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: HP
Product Name: HP Laptop 15-ef0xxx

[Schwarzer Kater]

You are welcome.

What is the exact name/model number/type of your HP laptop?

Numlock=on in an sddm configuration file sets NumLock for sddm only.

Here are some general possibilities for "activating NumLock on bootup": https://wiki.archlinux.org/title/Act...lock_on_bootup

This could also be too general of an idea, but did you try erasing your user's caches, logging out and in again after this and then trying the System Settings again?:
Best done from another user account or a tty: sudo rm -r /home/your_user_name/.cache/*

[oshunluvr]

Not sure if you're just making typos - but it's numlock not numblock

sddm.conf should contain something like:

[Autologin]
Session=plasma
​
[General]
Numlock=on

From what I've read you have to have both sddm,conf and plasma set to numlock=on

As far as the LED, possibly a boot setting could fix that but you didn't tell us the model of HP.