Prior to filing a bug myself I searched launchpad for "num lock", so this bug with "numlock" in the title did not show up. The bug I filed is Bug #1846249. I am experiencing the same issue under 19.10 when logged in with Wayland. The problem is not present in an X session. In fact I can do the following:
(1) boot the computer with the numlock key (led) active (2) login to a Wayland session and the number keys won't work but num key led is on (3) log out (not reboot) and log into an X session (4) number keys work immediately (have not touched numlock key and led is still on) (5) log out (not reboot) and lot back into a Wayland session (6) number keys do not work unless I hit numlock key which turns off the numlock led The relevant gsettings for numlock can be found in my bug report as well as some other logs and information: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1846249 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1845031 Title: gnome not remembering numlock state in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
