http://bugzilla.opensuse.org/show_bug.cgi?id=901916 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED Assignee|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com --- Comment #1 from Stefan Dirsch --- /etc/X11/xdm/Xsetup: [...] # # Enable Numlock if set # if test -r /var/run/numlock-on && type -p numlockx > /dev/null ; then numlockx on fi [...] In the past /etc/init.d/kbd touched /var/run/numlock-on if appropriate. But there is no longer such a kbd script. It has been replaced by using systemd's localectl. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 --- Comment #3 from Stefan Dirsch --- Also see the warning: ## Type: list(bios,yes,no) ## Default: bios # # NumLock on? ("yes" or "no" or empty or "bios" for BIOS setting) # This setting may interfere with GNOME /desktop/gnome/peripherals/keyboard/remember_numlock_state GConf key. KBD_NUMLOCK="bios" This key is set by default (at least on sled12), so it would overwrite the numlockx setting with the numlock state of previous session anyway. Not sure about other desktops though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #5 from Wolfgang Bauer --- I can confirm this problem on two 13.2 systems here (although it worked fine on one of them until recently). The problem seems to be that /etc/sysconfig/keyboard is missing from the initrd, so systemd-vconsole-setup apparently cannot read it and doesn't create /var/run/numlock-on when it should. Adding /etc/sysconfig/keyboard manually to the initrd (via dracut's -I switch) fixes the issue here and turns on NumLock like in earlier versions. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 Bob Williams changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |linux@barrowhillfarm.org.uk -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 --- Comment #9 from Bob Williams --- Any progress with this bug? My 13.2 system running KDE 4.14.4 still sufferes from it. After booting, if I press Numlock at the KDE login screen, I can use the number keypad to enter my passsword. Once the KDE GUI is up and running, the keypad no longer works, even after toggling the Numlock key. However, if I the switch to a virtual tty (Ctrl + Alt + F2) I can enter numbers on the command line using the number keypad. Switching back to the graphical environment (Ctrl + Alt + F7) disables the number keypad again. Bob -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 --- Comment #11 from wsxy162 chen --- I'm using Gnome 3.14,and I also have this problem. When I try this command "gsettings set org.gnome.settings-daemon.peripherals.keyboard numlock-state on",it doesn't work meanwhile it does turn on the numlock when you reboot or relogin in arch. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=901916 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #12)

Still, I'd like to ask @Thomas Renninger, can we fix that, please? I.e. can you add /etc/sysconfig/keyboard to the initrd?

For me, this works fine on all (KDE) systems I tried it on (unless you have different user settings of course), and it is necessary AFAICT.

Actually this does work now since the latest systemd/udev update, even without /etc/sysconfig/keyboard in the initrd. This patch adds an udev rule that calls systemd-vconsole-setup again during boot when / is already mounted: https://build.opensuse.org/package/view_file/openSUSE:13.2:Update/systemd.34... I tried on a system with the radeon driver and on one using the proprietary nvidia driver, with and without "nomodeset", and it worked fine every time. So it seems /etc/sysconfig/keyboard is not needed in the initrd any more. Closing as FIXED therefore... But I have no idea whether there maybe would be some corner cases where it still might be necessary though. AIUI that udev rule only triggers if the kernel switches to fbcon, I don't know whether this is always the case. -- You are receiving this mail because: You are on the CC list for the bug.