From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20020625 Description of problem: I switched my video card from an S3 Trio64 (generic) to an ATI Mach 64 VT (264VT). Kudzu correctly detected it, but then called Xconfigurator and reset my keyboard from Estonian to US. Version-Release number of selected component (if applicable): How reproducible: Didn't try Steps to Reproduce: 1. Installed Limbo on a PC with an S3 Trio64 video card. I didn't like how poorly it worked. 2. Shutdown the computer and replaced the card with the ATI Mach 64 VT. 3. Started the computer. 4. Kudzu detected the new card and started Xconfigurator to prompt for a preferred resolution, color depth, and whether to start X at boot time. 5. Kudzu ended; X started 6. Everything looked fine until I entered my password. Further testing showed that my keyboard was configured as US. It is still Estonian on virtual consoles. Actual Results: Keyboard configuration changed to US. Expected Results: Keyboard configuration to remain Estonian. Additional info: #rpm -q kudzu Xconfigurator kudzu-0.99.58-1 Xconfigurator-4.10.7-3
Hm..., this is because kudzu doesn't read the keyboard info, I think, and Xconfigurator may default to US keyboard. Well, future versions of kudzu will call redhat-config-xfree86; this may solve the problem, in that it will probably use a different algorithm.
Yeh, I noticed the movement toward using redhat-config-xfree86, so this bug can have a low priority until that movement is complete. (That is, assuming this movement is complete before Limbo leaves beta.) I have confirmed that Xconfigurator is the guy who resets the keyboard to US. I re-installed the system with one monitor and used Xconfigurator to use a second monitor and the keyboard settings changed at the same time.
I haven't seen this problem since I originally reported it. I don't think we need to worry about it anymore.