https://bugzilla.novell.com/show_bug.cgi?id=746595 https://bugzilla.novell.com/show_bug.cgi?id=746595#c39 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |sbrabec@suse.com --- Comment #39 from Frederic Crozat <fcrozat@suse.com> 2012-06-13 17:08:01 UTC --- (In reply to comment #38)
and the reason why 8 of my 10 12.2 installations and all except 1 of my dozen or so 12.1 installations default to sysvinit-init boot. Systemd would get a whole lot more testing here, and a whole lot less attention paid to sysvinit bugs, if this actually got fixed.
please refrain from such comments in bugzilla in the future. I make your message more difficult to understand and doesn't give incentive to anybody on fixing bugs. Stay focused on the bug itself and nothing else. If you don't say which package of systemd is installed on your system, it is impossible to guess if you have a version which is supposed to contain the fix or not and how you are testing exactly and what is exactly broken. So far, I've tested on Factory, with systemd-44-5.1 (and on 12.1 maintenance update, they are similar) and numlock is correctly set for X session. For tty, numlock is enabled correctly but the leds itself doesn't seem to be set properly, as stanislav noted in comment34. When starting in runlevel 3 directly, it looks like the numlock is kind of set (login complains about "numlock is off") but neither keyboard nor leds are set properly. Starting X ensures leds is set properly. Stanislav, it looks like something is missing, compared to sysvinit, in the runlevel 3 setup. -- 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.