Bugzilla – Bug 154717
Bad keyboard selected on update installation
Last modified: 2006-03-03 14:21:17 UTC
I have selected Czech locale and update selected English keyboard. How to reproduce: - Boot from CD. Select Czech in grub menu. - Press Cancel in YaST (probably not relevant). - Select Network installation in console (probably not relevant). Console uses Czech keyboard. - Select Update (I was uptdating from updated beta3). - Select additional sources. Actual results: Additional source dialog uses English keyboard. Expected result: Additional source dialog uses Czech keyboard. Additional info: In the next step (installation summary) YaST correctly decided to install Czech locale.
Please, attach the log files.
Looks like that "Cancel" was relevant. Looking to the logs, YaST only calls "setxkbmap -layout cz,us", maybe linuxrc changed the layout for some reason?
Unlike the first time, yast doesn't run loadkeys the second time. Maybe it doesn't like the 'Keytable' entry in /etc/install.inf?
When I was choosing FTP installation in the text console, the keyboard was Czech. Only X keyboard was English.
Well, yes. But something is causing yast to not set the keyboard. My guess would be the Keytable entry, as it's not there the first time.
When 'Keytable' contains cz-us-qwertz.map.gz, yast doesn't call loadkeyes again - this is correct. Why do you think yast should do something else?
If you follow that thought: why does it call loadkeys at all, then? Anyway, this report is about the wrong keyboard in X11. And X is started after linuxrc, so I'm not exactly sure how I can help. And as yast 'fixes' the setting in later dialogs, my guess would be it just forgets to set it in time.
If I get it right, the keyboard mapping is not fixed, yast just knows correct value of language. The problem might be that after new start of x server, setxkbmap is not called (together with not calling of loadkeys) when Keymap is found. Yes, this will be it, I was confused by your remark that YaST didn't call loadkeys (which it shouldn't).
No, it's even different problem in Keyboard.ycp :-( Fixed package submited to stable, Stanislav I would be happy if you could test it again with next beta :-)