Bug 183022
Summary: | Keyboard mapped incorrectly during installation | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Fred New <fred.new2911> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED RAWHIDE | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | ||
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: | 2006-02-28 08:55:23 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: | 150222 |
Description
Fred New
2006-02-25 14:19:10 UTC
I have the same problème with fr_ch keyboard. It's very ennuying when you chose you root password... I take only digit but's is not a solution. I can't duplicate this problem for the fr-CH keyboard. (But I'm using and Estonian keyboard, so my scan codes may be wrong.) This bug deals with the early part of the installation before the installer has been able to read any of the installation media besides the isolinux boot kernel and its initrd.img. It may be wrong to blame Anaconda for this bug. Does it work properly on the console after installation? This is something that keeps happening somewhat spuriously on various keymaps and I'm wanting to lean towards blaming something about the compose process. Yes, the virutal consoles are correct once the installation completes. I just tested rescue mode and it has the same key mapping problem. I had "rescue mode keymaps/LANG?" on my whiteboard. The question mark was a reminder to me to figure out if that stuff applied to rescue mode. This bug answers my question. Jeremy, if you want me to take this one, I will. The changes I'm making now should hopefully fix this. If you could try with tomorrow's (20060228) development tree to confirm that things are good, I would appreciate it. Oops. The initrd.img (and vmlinuz) dated 27-02-2006 don't have this problem while the files issued with FC5T3 dated 16-02-2006 have the problem. I wish I would have thought of trying the development tree earlier so I could tell you when this got fixed. |