Ok, I'll put this here, but there are different packages affected ... There are also many other keyboard bug entries, but I didn't find something like this (ie. keyboard works partially correct). Using the latest (4.0-0.29 and 3.3.6-28) X packages (I have a ATI graphics card which uses the 3.3.6 X server) there are some problems with german keyboards: backspace and delete do not work. Produce beep and ~ If the shells (xterm or konsole) are not started as login shells, the german "umlaute" (dv ...) do not work. Therefore these programs should always be invoked using -ls (eg. in the KDE panel or the KDE menu). The right "Alt" key is called "AltGr" here. Necessary for things like "|", "{" etc. This does not work either. Wenn used in a login shell it produces "1/4", in a non login shell it brings you to the first entry in your history (in the KDE "execute command" window it does not do anything).
This defect is considered MUST-FIX for Winston Beta-5
Bero, can you verify this?
I can't on my installation - but this may be an issue with anaconda and/or Xconfigurator creating wrong keyboard configs (I'm just copying my old config files around every time, much too lazy to calculate new optimal mode lines every time I reinstall ;) ). Michael, can you attach your XF86Config please?
I'm just downloading Beta 4. Will try to reproduce it this weekend and will put a summary here.
This defect has been re-classified as MUST-FIX for Winston Gold-release
This is mostly fixed in Beta 4. Only one issue is still remaining - kdm doesn't treat "AltGr" correctly, therefore things like "~" don't work. Moving this bug to kdebase.
Just in case you'd like to have a look at it, here's the keyboard section of XF86Config. I just left out the comments, the rest is unchanged, ie. just how anaconda and Xconfigurator generate it. Section "Keyboard" Protocol "Standard" AutoRepeat 500 5 LeftAlt Meta RightAlt Meta ScrollLock Compose RightCtl Control XkbRules "xfree86" XkbModel "pc104" XkbLayout "de" XkbVariant "nodeadkeys" XkbOptions "" EndSection
This defect is considered MUST-FIX for Winston Release-Candidate #1
The kdm problem is fixed in rawhide; however, many people are still reporting X keymap problems after fresh installations. Looks like anaconda creates broken settings for German keyboards; running Xconfigurator helped when this occurred. In particular, the Alt Gr key doesn't seem to work in some installs (it's needed to produce important characters like @ or | on German keyboards) with anaconda's X configuration.
Ok, think we can close this, right? There are other bugs that deal with that german keyboard problems. I did some testing on that and made comments to the appropriate bug reports. For example, see bug 13525.
This works now, on an anaconda-GUI installed machine with a German keyboard.
The kdm "AltGr" problem is still there in RC1 (text KDE workstation installation). Reopening.
bero, please try and get this addressed before RC2.
What happens if you switch it to use pc101 instead of pc104?
Same problem. The problem also exists with XFree86 4; the config file there only says Xkblayout "de" no model stpecified then.
Just noted that this also happens in the KDE quick run ("run command") box, again.
This defect has been re-classified as SHOULD-FIX for Winston Gold-release
Is this related to bug number 13600?
Hm, don't think so. There where a number of bugs similar to bug #13600 (which I think should be a duplicate of some another bug, will try to find it). This problem occurs also if Alt-Gr works in normal X apps, only kdm and KDE "quick launch" don't treat them correctly.
This seems to be a very weird X problem: It happens in kdm, gdm and the KDE quicklaunch, and stops happening as soon as you do anything (e.g. in kdm, click on the selection combobox and it works, in gdm click on the menu and it works). Since it's happening both in kdm and gdm, it's almost certainly some weird Xlib issue. Seems to happen in all unmanaged windows requiring input.
*** Bug 31810 has been marked as a duplicate of this bug. ***
*** Bug 31811 has been marked as a duplicate of this bug. ***
*** Bug 18792 has been marked as a duplicate of this bug. ***
Changing the summary to match the portion of the problem that is still present.
After consulting all of the bug reports linked to in this one I am almost certain that this was the bug in the installer calling setxkbmap incorrectly when enabling/disabling deadkeys. This problem is now fixed in anaconda in rawhide. try: setxkbmap -model de -layout basic and/or setxkbmap -model de -layout nodeadkeys If either fixes the problem, this is definitely the deadkeys bug from the installer under a different guise. Another as of yet uncorrected bug is that disabling deadkeys doesn't always disable ALL dead keys due to bugs in the keyboard layout tables.
Seems to work fine in Fairfax. Changing to CURRENT.