Bug 80141
Summary: | Anaconda doesn't support new xkb model | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Leonid Kanter <leon> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | aleksey, ekanter, katzj, mharris, milan.kerslager |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 18:50:29 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
Leonid Kanter
2002-12-20 16:40:24 UTC
> This list is actually a list of layouts that use non-latin1 characters
> and with new model must always be loaded together with "us" layout.
Ideally, it should also be capable of updating existing XF86Config on upgrade.
Changing version to Beta4 IMHO this deserves severity: high since it is capable of making X unusable (until one figures out how to fix the config). I think that this should actually be an XFree86 bug. I have no way of guaranteeing that the user will install/upgrade redhat-config-keyboard, so there's no guarantee that the migration will take place. I think that XFree86 should make this change when it is upgraded. Now, redhat-config-keyboard *does* need to be changed to be able to write out XF86Config that contains both keymaps for the languages that need them (bug #82440), but the actual migration of the XF86Config file on upgrades needs to be done by XFree86 itself. I'd like to see how that is possible, without requiring weeks of development and 400kb RPM post install scripts. Not likely going to be done by XFree86. I consider this entirely a config tool issue. Maybe not full logic, but simple inserting comment to XF86Config near keyboard section. If you apply patch listed above, everything should work exactly like in 4.2, but it would be ignoring of new xkb features. There is one more way: disable X keyboard configuration in inslaller and let to the user configure keyboard himself using user-space graphical gnome configuration tool - gswitchit, which is not included to distribution yet. kxkb from kde also works somehow. I think yes. Looks like the problem will be solved in bug 82440, if anaconda use the same code. *** This bug has been marked as a duplicate of 79287 *** mharris: We have no guarantee that the user will run the config tool on an upgrade. Firstboot doesn't run on an upgrade and anaconda will not modify the XF86Config file on an upgrade. There's no guarantee that the user has redhat-config-keyboard installed, so the problem can't be solved by the config tool. I have modified redhat-config-keyboard to do the right thing once it has been run, but there's no way to make it run on an upgrade. The way I see it, the only guarantee that we have is that the %post section of XFree86 will be run if XFree86 is upgraded. For example, imagine that I have an 8.0 system that uses the 'ru' keymap and I upgrade XFree86 by hand, including all the packages that will require. When I restart X, BAM!, I can't toggle to a us keymap anymore. XFree86 should be able to change that one line in the config file without requiring that the user run some other config tool. I know it's difficult, but don't you think that's the right thing to do? IMHO the only real alternative to messing with configs on upgrade (which might have undesired implications) is to mention the issue in the release notes (see bug 82440 comment #5) and/or pop up a warning in anaconda, possibly also asking whether user wants anaconda to regenerate the config. *** This bug has been marked as a duplicate of 79287 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |