GNOME Shell 3.34.0 on Wayland
Logitech Illuminated Keyboard
I set this gsettings:
org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state true
When I enter in Gnome Shell the numlock LED is on but it doesn't work like numeric pad, it works the arrows keys, etc...
This has affected me as well since I updated to F31.
To help clarify:
F30 behavior: The state of numlock is remembered between reboots.
F31 behavior: Numlock always starts in the disabled state after a reboot.
Pressing numlock functions normally, but its almost like the remember-numlock-state
gsetting only saves the state of the LED not the actually functionality of numlock.
For example if numlock is ON and the LED is ON and then I reboot, when my desktop
shows back up the numlock will be OFF but the LED will be ON. From that point
pressing numlock will toggle it ON, but the LED will go OFF.
(In reply to Matthew Bunt from comment #1)
Exactly same problem with the remember-numlock-state and numlock-state gsetting. It changes the state of LED but not the numlock behavior itself.
I am experiencing the same behavior. It seems that F31 saves the state of the LED, but always starts with numlock turned off. Therefore, if the numlock led is on at login, it will be out of sync with the actual behavior (if led is on, num lock is off; if led is off, num lock is on). However, if the led is off at login, then it will be in sync with behavior (if led is off, num lock is off; if led is on, num lock is on). This seems to be limited to Wayland for me. If I log into an X session, the problem is not there.
I should have noted that I am using a DAS Keyboard Prime 13. I have tested the keyboard with nkey rollover disabled and enable and there are no changes. I experienced this same issue with Ubuntu 19.10 beta. I was previously using Ubuntu 19.04, and the issue was not present, even when using the Wayland session.
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 31 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.