Red Hat Bugzilla – Bug 76081
Pressing AltGr generates garbage
Last modified: 2007-04-18 12:47:39 EDT
In 8.0, whenever I press AltGr on my (Swedish) keyboard (in order to compose
some other character such as @ by subsequently pressing another key), I seem to
get random garbage (such as 0, ", and unprintable characters), in addition to
the composed character I wanted.
Pressing *only* AltGr also generates the same garbage. This happens both in
console mode and in X. I can reproduce this on at least three machines.
What does 'locale' say?
Output of "locale":
I don't see that here. Please give me a detailed 'steps to reproduce'. Thanks.
1) Install 8.0 system from scratch
2) Pick Swedish keyboard at the installation time
3) Use defaults in other settings
That should be it. On such a system, when I press AltGr only on the terminal, I
get 0, and in the GDM login box and other X applications I get ". When I press
AltGr in addition to a second dead key, I get the 0 or " garbage in addition to
the dead key character.
The contents of my /etc/sysconfig/i18n:
I still can't reproduce it, although I don't have a Swedish keyboard. I tried
those steps (with a UK keyboard), and dead keys work fine. For example, AltGr-[
a produces an a with an umlaut.
Since you see this in applications other than bash, it can't be a bash bug.
Reassigning to redhat-config-keyboard.
bfox: Can you reproduce this problem?
This bug is a duplicate of:
I got the same problem using RedHat Linux 7.1, 7.2 and 7.3 updated to the latest
kernel (2.4.18-17.7.x) using up2date. The keyboard layout used here is
"fr-latin1". Same problem too with RedHat 8.0.
Pressing the right Alt key (AltGr) prints "0" on the console. Under X AltGr
Oh I forgot, as nicolas(dot)mailhot(at)one2team(dot)com say at
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=74759 , this problem only
occurs when "NumLock" is on when working with the console. If NumLock is off, no
garbage characters are printed on the screen (with console).
When working with X, the '"' are still displayed whenever NumLock is on or not.
Marking as duplicate.
*** This bug has been marked as a duplicate of 71136 ***