[Bug 813902] New: /etc/init.d/kbd failing due to loadkeys option incompatibility
https://bugzilla.novell.com/show_bug.cgi?id=813902 https://bugzilla.novell.com/show_bug.cgi?id=813902#c0 Summary: /etc/init.d/kbd failing due to loadkeys option incompatibility Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: lserni@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 The /etc/init.d/kbd uses in several places the syntax: loadkeys -C "$KBD_TTY" where KBD_TTY contains up to six space-separated ttys. But the -C option of loadkeys only accepts one console at a time, therefore the script fails when loadkeys complains that the file "/dev/tty1 tty2 tty3 tty4..." can not be opened. Reproducible: Always Steps to Reproduce: 1. type the command: loadkeys -C "/dev/tty1 /dev/tty2" it 2. type the command: loadkeys -C "/dev/tty1" it Actual Results: Couldn't open /dev/tty1 /dev/tty2 Loading /usr/share/kbd/keymaps/i386/qwerty/it.map.gz Expected Results: Loading /usr/share/kbd/keymaps/i386/qwerty/it.map.gz Loading /usr/share/kbd/keymaps/i386/qwerty/it.map.gz The solution I found was to convert the syntax to a for cycle in the kbd script: for tty in $KBD_TTY; do loadkeys -C $tty ... done instead of loadkeys -C "$KBD_TTY" ... Possibly the line above only activates in my setup (I have an Italian keyboard but en_US locale), but it is still wrong. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c
Xiaolong Li
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c1
Bruno Friedmann
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c2
--- Comment #2 from Leonardo Serni
The /etc/init.d/kdb is not used with systemd (was already the case in 12.2)
systemctl status kbd.service kbd.service Loaded: masked (/dev/null) Active: inactive (dead)
So the root cause of your trouble is elsewhere
I see. My distro was born as a 11.3 if I recall correctly, and I have updated it at every new release with never a problem, so I hadn't thought of trying with a clean install. Possibly the kbd service was left behind and not deactivated. I'll try disabling it altogether, and see where the console fonts get loaded now. Thanks. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c3
--- Comment #3 from Leonardo Serni
The /etc/init.d/kdb is not used with systemd (was already the case in 12.2)
systemctl status kbd.service kbd.service Loaded: masked (/dev/null) Active: inactive (dead)
So the root cause of your trouble is elsewhere
Yes and no. I have now tried with a clean 12.3 install on an empty VM (text mode install, no GUI). The kbd.service does indeed report "dead", the kbd script is not invoked, and no console font is set. Numlock and keyboard repeat rate also seem to be no longer accessible. In yast2 "System Services", under runlevel, I find the kbd service listed as active (the text actually even says "(don't disable!)". In Expert Mode, it says the service is not running, and cannot be started due to an "unspecified error". So yes, the cause of my troubles with the console font is that I want to change the console font :-) . But I don't want to accept that the correct approach is "to do without". So, I have now unmasked and reenabled the kbd.service in systemd (I had to create a "kbd.service" systemd config stanza for it to replace the symlink to dev/null), and corrected the errors in loadkeys that were present in the 12.3 /etc/init.d/kbd (as above: replaced the single call to KBD_TTY with for t in $KBD_TTY; do...; and the same with $TTY) . The system appears now to be working; repeat rate, leds, map and font all get loaded as expected. Haven't tried much, and I am not using X, so I can't guarantee some weird interaction with X/xdm might not take place. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c4
Petr Gajdos
https://bugzilla.novell.com/show_bug.cgi?id=813902
https://bugzilla.novell.com/show_bug.cgi?id=813902#c5
--- Comment #5 from Petr Gajdos
/etc/init.d/kdb is dropped completely.
numlock, capslock, etc. issues related to systemd should be fixed in 13.1
Aehm, it's not, sorry. See bug 802189 comment 6 for details. I will add you into cc of this bug. -- 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.
participants (1)
-
bugzilla_noreply@novell.com