Bug 78060
Summary: | Installation - Norwegian keyboard is not working. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Inger Karin Haarbye <inger> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | bfox, david.balazic, katzj, menthos, ra |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-08-30 19:30:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 79578 |
Description
Inger Karin Haarbye
2002-11-18 16:20:57 UTC
Brent -- any ideas here? It uses a Norwegian keymap during the graphical install for me on an 8.0 install, and I don't think anything has changed in that code since then. haarbye, is this a cdrom based install? In 8.0 Norwegian keymap worked for me too (it usually works!), but in 8.0.90 I get US keyboard in the dialogs. After installation has finished, norwegian keyboard works fine. And - Yes, it is a cdrom based install. katzj, do you have any cd's of beta1 that we can test? I don't have any over here. Ok, I've confirmed that the bug occurs in beta1. I'll have to dig a little deeper to find out why it's just started happening. However, it does change the keymap to Norwegian on the console, just not in X. Hmm.... katzj, it looks like the bug is in rhpl somewhere. In the getNext() function of keyboard_gui.py, we call kbd.activate. The activate() function should call loadkeys (which seems to work) and then fork a call to setxkbmap(this seems to be failing for some reason). The only thing that seems strange to me is that loadkeys is called with an executils call while setxkbmap is forked and os.execv'd. Any idea why? Actually, this happens for all keymaps not just Norwegian. I'm a little confused because the call to setxkbmap is clearly there, but it looks like it just isn't being called at all. ?!? The problem still persists in 1212.nightly. katzj, I really don't have any idea why this is failing. Do you? I think it might well be fixed in the current tree -- Brent, one of us should try to remember to try this out today Testing it now... Nope, still broken with re1219.nightly. Looks fixed in re0103.nightly. Closing as Rawhide. It's back again in Beta4 I've verified that this bug has returned. Jeremy: any idea what is causing this? Is it an X problem? I don't think that there's any way that this is a redhat-config-keyboard problem. The keymap is getting set properly on the console via 'loadkeys', but 'setxkbmap' seems to not be working. *** Bug 82093 has been marked as a duplicate of this bug. *** I don't see how it could be anything other than X assuming setxkbmap gets called with all of the right arguments. I'm going to transfer this bug to XFree86. setxkbmap works after reboot, so it seems like something is wrong with calling setxkbmap only during anaconda. redhat-config-keyboard is calling setxkbmap with the exact same arguments during anaconda as it does after reboot. The bug is that calling setxkbmap during anaconda has no effect. This bug has disappeared and reappeared a few times. redhat-config-keyboard has not changed in the way that it calls setxkbmap. Well now with the re0129.nightly tree, setxkbmap is working in the installer. Yet I know for a fact that it was not working in yesterday's tree. This bug has disappeared and reappeared two or three times now. What in the world is going on? Changes in -fPIC in X builds? If not, then it must be some non-X thing. Either way it looks fixed now, so I'm closing to MODIFIED. Resolve as RAWHIDE once satisfied it is fixed. *** Bug 81052 has been marked as a duplicate of this bug. *** I'm seeing no problems making use of a German or French keyboard in both TUI and GUI installations using the re0206.nightly tree. I've added a GM test case to cover this, so if it does recur, we'll catch it. Jay, you didn't catch it :-( It is back in RHL9. Tried Slovenian and German keyboard, none of them works. ( boot cd1 into GUI install select Slovenian kbd layout type something in the disk druid dialog -> it is US layout, not Slovenian kbd layout on text console VT1-VT6 is correctly Slovenian ) As I said , this is with Shrike ( Red Hat Linux 9 ). It is/was the same with beta5/phoebe3/8.0.94 It is back in 9.0.90 ( Cambrigde alpha1 ) Again problem setting Slovene kbd in X during GUI install. When selected, it is set for the text console , but not in X. Log on VT3 : * running ['/usr/X11R6/bin/setxkbmap', '-layout', 'us', '- model', 'pc105', 'option', ''] * moving (1) to step welcome * moving (1) to step betanag * moving (1) to step language * moving (1) to step keyboard * running ['/usr/X11R6/bin/setxkbmap', '-layout', 'si', '-model', 'pc105', '- option', ''] Maybe the empty option parameter is problematic ? Why/how is this an XFree86 bug? Weird...this seems to work for me in the latest nightly installer. Problem still there in alpha2 ( tried to set slovene keyboard layout ) This isn't an XFree86 bug. Please read the setxkbmap manpage and follow it to a tee. If there is a bug in setxkbmap, please provide the exact commandline which triggers it and step by step instructions on how to reproduce it in an installed environment, so that it can be investigated. If there is a bug in setxkbmap, which I definitely can't see from this bug report, I need to be able to investigate it on a sane system with debuggability and I can't do that while anaconda is running during installation. Additionally I note that this "problem" is coming and going randomly as you describe above, and during all of this time, nothing in XFree86 nor setxkbmap has changed _at_all_. Therefore I consider it to be an invocation problem or some other non-X weirdness. *** Bug 91801 has been marked as a duplicate of this bug. *** |