[opensuse-factory] /etc/sysconfig/keyboard KBD_NUMLOCK="yes" ignored in TW20171214
This always initialized numlock ON on the vttys in the past. It doesn't in my latest installation, even though BIOS is set to ON. Is this a new expectation, or a bug? I see nothing open or closed in BZ that was new in past year. If expected, what's the new method? -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I think it has stopped working for a long time. Some people who never use the VTs will rush now to offer advice on how to configure kde or sddm. What I have found to be working is to add the folowing to /etc/init.d/boot.local: for tty in /dev/tty{1..9}; do setleds -D +num < $tty done -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 19 Dec 2017 01:15:22 -0500
Felix Miata
This always initialized numlock ON on the vttys in the past. It doesn't in my latest installation, even though BIOS is set to ON. Is this a new expectation, or a bug? I see nothing open or closed in BZ that was new in past year. If expected, what's the new method?
Bugzilla number? -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Marcus Rückert composed on 2017-12-19 12:38 (UTC+0100):
On Tue, 19 Dec 2017 01:15:22 -0500 Felix Miata wrote:
This always initialized numlock ON on the vttys in the past. It doesn't in my latest installation, even though BIOS is set to ON. Is this a new expectation, or a bug? I see nothing open or closed in BZ that was new in past year. If expected, what's the new method?
Bugzilla number?
As I wrote, I found none. I didn't file one, because 1-I don't know if this is a new expectation, as other things have been being relocated from /etc/sysconfig to e.g. /etc/alternatives or /etc/default. 2-I have multiple TW installations, and it only happens on the (fresh) UEFI boot one. -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-12-19 03:18 PM, Felix Miata wrote:
Bugzilla number?
As I wrote, I found none.
https://bugzilla.opensuse.org/show_bug.cgi?id=1010880 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Χρήστος Γουρδούπης composed on 2017-12-19 16:38 (UTC+0200):
Felix Miata wrote:
Bugzilla number?
As I wrote, I found none.
https://bugzilla.opensuse.org/show_bug.cgi?id=1010880 That's an old 42.2 bug. I have many 42.2, 42.3 and TW installations, and mine is a brand new behavior that has nothing to do with Xorg. I've always had to separately configure DM and X to turn on NUM in graphical.target. Here /etc/sysconfig/keyboard has only ever worked for the vttys, and now it does not, but only on the two new host gb250 installations booting UEFI. I've been using *SUSE since 8.0, and until now, /etc/sysconfig/keyboard has always been sufficient - I've never needed setleds except in other distros. TW20171216/4.14.6-1.5 and 42.3/4.4.92-31.1 MBR/BIOS host gx780, among my many other 42.2, 42.3, 15.0 and TW (non-UEFI) installations, is still obeying /etc/sysconfig/keyboard's KBD_NUMLOCK="yes". -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
That's an old 42.2 bug.
Like I said, it's old
my many other 42.2, 42.3, 15.0 and TW (non-UEFI) installations, is still obeying /etc/sysconfig/keyboard's KBD_NUMLOCK="yes".
That's strange, because if I do: grep -sR 'KBD_NUMLOCK' /etc /usr I come up with nothing. But look, the bugzilla is heating up. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Christos Gourdoupis composed on 2017-12-19 22:23 (UTC+0200):
That's an old 42.2 bug.
Like I said, it's old
my many other 42.2, 42.3, 15.0 and TW (non-UEFI) installations, is still obeying /etc/sysconfig/keyboard's KBD_NUMLOCK="yes".
That's strange, because if I do: grep -sR 'KBD_NUMLOCK' /etc /usr I come up with nothing.
It's there in my two fresh 15.0 and TW installations.
But look, the bugzilla is heating up.
Indeed. It looks like Stefan Dirsch noticed this thread, and why: https://bugzilla.opensuse.org/show_bug.cgi?id=1010880 -- "Wisdom is supreme; therefore get wisdom. Whatever else you get, get wisdom." Proverbs 4:7 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2017-12-19 10:45 PM, Felix Miata wrote:
It's there in my two fresh 15.0 and TW installations.
I mean nothing that uses it.
But look, the bugzilla is heating up.
Indeed. It looks like Stefan Dirsch noticed this thread
Thank you for bringing this up in the list. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Christos Gourdoupis -
Felix Miata -
Marcus Rückert -
Χρήστος Γουρδούπης