https://bugzilla.novell.com/show_bug.cgi?id=746595 https://bugzilla.novell.com/show_bug.cgi?id=746595#c2 --- Comment #2 from Felix Miata <mrmazda@earthlink.net> 2012-02-13 16:56:08 UTC --- As long as systemd is unable to do at least as well as sysvinit did regarding NUM state, and kernel devs continue after close to three decades to disrespect the BIOS state for NUM, systemd won't be usable. If it was up to me, it would be impossible for any keyboard with separate cursor and NUM pads to not produce NUM characters from the NUM pad, and the NUM key if retained at all would be permanently and unalterably on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.