Bug 337238

*** Bug 337359 has been marked as a duplicate of this bug. ***

In Beta 3 still no working Cyrillic keymap. Setted by default ru1.map.gz dont work at all. Only spaces typed instead of cyrillic chars.

Created attachment 216175 [details]
UTF variant of ru1.map.gz

I'we made itf version of ru1.map.gz that used by default in russian installation. I'we just replaced ASCII codes by UTF keycodes. All alphabetical key looks work fine, functional works too.

Please test if it works fine for ou by loading keymap with command 
loadkeys ru1-utf.map.gz 
or by placing it into /usr/share/kbd/keymaps/i386/qwerty/  and setting 
KEYTABLE="ru1-utf.map.gz"
in  /etc/sysconfig/keyboard 

Created attachment 216178 [details]
ru1_win-utf.map.gz - winkeys ru1-utf variant

Made some changes to get more often using russian layout called winkeys in X. In that layout Shift +7 types '?', comma and period located near right shift.

Have tested this keymaps and got other problem, keymaps works only when loaded with loadkeys command, but when loaded from /etc/sysconfig/keyboard with rckbd script layots dont switch, or switch, but cant input anything in russian, cursor just stay in one place.

added data/keymaps/i386/qwerty/ru1_win-utf.map
submitted to stable.

thanks!

Created attachment 216359 [details]
ru-utf.map.gz, used and workinkg fine in all others linux distribution

Juergen, please read my post above, this keymap works fine only loaded directly with loadkeys command, and dont work when loaded with script. The same thing happened with ru-utf.map.gz that used in all other distribution. It works when loaded with loadkeys and cant switch layout when loaded by script, but in all other distribution this keymap works fine.

And another one question: Where from all this russian keymaps /keymaps/i386/qwerty/ru*, it all for 8-bit local terminals.

/keymaps/i386/qwerty/ua-utf.map
that already exist in opensuse kbd packages have the same problem. It works fine loaded by loadkeys command and dont work when loaded by /etc/init.d/kbd script.

Adding suggested keymaps to the package is what I *can* do.
I cannot debug the rc issue.

I have found that keymaps working fine when loaded by script if it runned from text terminal and dont work correctly if it runned from an X terminal.

Just test it. Set some utf keymap in /etc/sysconfig/keyboard, for example bg_pho-utf8.map.gz, ua-utf.map.gz or one of attached. Next run rckbd restart from text terminal. Test keymap, just switch layout by Ctrl+Shift or by two Alts and try to type. It should work. Next run rckbd restart from an X terminal and try to switch layout in text terminal and type, it cant type anything.

When rckbd running on boot result the same as I run it from X terminal and keymap dont work.

I think it problem in /etc/init.d/kbd script or in loadkeys.

Maybe you should reassign bug to someone who can debug that script and loadkeys? 

Mike, any experience with loadkeys?

I can reproduce that if I use the following settings:

mfabian@magellan:~$ grep KEYTABLE /etc/sysconfig/keyboard
# e.g. KEYTABLE="de-latin1-nodeadkeys", "us" or empty for US settings
KEYTABLE="ru1_win-utf"
#  or KEYTABLE will be used then -- most keyboard maps don't have a
mfabian@magellan:~$ grep CONSOLE_FONT /etc/sysconfig/console 
CONSOLE_FONT="Cyr_a8x16.psfu"
mfabian@magellan:~$

The Russian keyboard works if “sudo rckbd restart” is executed on the
Linux console but it does not work if “sudo rckbd restart” is started
from a terminal running under X.

But why is it necessary to run this under X?

Thanks Mike for testing this.
rckbd restart is not supported from within an X terminal.
rckbd only works for the text console and must not be called while X is running.

rckbd should work on reboot just the same as when called manually from a console.

Now I tested booting. I booted 3 times:

- once everything worked
- two times the Russian keyboard did not work showing the same
  symptoms as when running "sudo rcxkb restart" under X

I.e. I can reproduce the problem of the reporter probably most
of the time.

 

commenting out the line

    ( dumpkeys | loadkeys -C "$KBD_TTY" --unicode ) > /dev/null 2>&1

in /etc/init.d/kbd seems to make it work.

Probably, this line is not necessary when the keymap is already
a native unicode keymap like the reporter’s ru1_win-utf.map.gz.

But commenting this out might cause trouble
when using non-Unicode keymaps like de-latin1-nodeadkeys.

Looks like Werner fixed it ☺!

Created attachment 220160 [details]
werners-change.patch

Werners patch to fix this.

FIXED.