After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 758211 - On Wayland, keypad numlock status is not remembered
On Wayland, keypad numlock status is not remembered
Status: RESOLVED DUPLICATE of bug 757943
Product: gnome-settings-daemon
Classification: Core
Component: keyboard
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: Rui Matos
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2015-11-17 04:33 UTC by Jean-François Fortin Tam
Modified: 2015-11-17 16:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jean-François Fortin Tam 2015-11-17 04:33:05 UTC 
Not sure which component to file this on (GDM? gnome-shell? settings daemon?)…

When I boot my computer, the numlock light on my keyboard is on (as it should be). Once I reach the gdm screen, it turns off... and when I log into a gnome wayland session, it stays off and the numpad is deactivated (the keys behave as arrows instead).

This problem does not occur when running under the normal X11 session, as the session would restore the last state of the numpad numlock no matter what (and I remember this being a massive relief when it started working well like that some years ago).
Comment 1 Jean-François Fortin Tam 2015-11-17 04:40:09 UTC 
Yep, I can confirm that under X11, the process is as follows:

1. Numlock is active at boot/plymouth
2. Numlock gets turned off at gdm (which runs Wayland AFAIK)
3. Numlock gets turned back on by the X11 GNOME session
Comment 2 Bastien Nocera 2015-11-17 09:35:16 UTC 
That's not a regression.
Comment 3 Rui Matos 2015-11-17 16:13:07 UTC 

*** This bug has been marked as a duplicate of bug 757943 ***