Bug 476619

Summary: The AltGr key does not work
Product: [Fedora] Fedora Reporter: Joachim Selke <mail>
Component: java-1.6.0-openjdkAssignee: Lillian Angel <langel>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: low    
Version: 10CC: dbhole, langel, lkundrak, marc.saric, mjw
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: 2009-12-18 07:18:32 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:

Description Joachim Selke 2008-12-16 09:18:58 UTC
The AltGr key does not work for me in Java applications. I use a German keyboard layout, so e.g. pressing AltGr+7 should give the curly bracket {. Instead, I get 7. I tested several Java applications (e.g. /usr/lib/jvm/java/demo/jfc/Notepad/Notepad.jar) but always get the same result. I use java-1.6.0-openjdk-1.6.0.0-7.b12.fc10.x86_64. In other applications (e.g. gedit and firefox) the key works as it should.

There seem to be many different people having this problem but I was not able to find any Fedora bug report yet. Here are some links to other people's experiences:

http://forums.fedoraforum.org/showthread.php?t=206689
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=262

The problem doesn't seem to be exclusively related to openjdk. It also occurs with VMware products, which are not based on Java as far as I know:

http://communities.vmware.com/thread/172478
http://grumpyapache.blogspot.com/2008/12/vmware-and-key-maps-on-fedora-10.html

I filed this bug against openjdk since I don't know better at the moment.

Comment 1 Marc Saric 2009-02-21 14:15:51 UTC
This problem also occurs with Sun Java JDK 1.6_11 installed via the installation istruction on http://www.mjmwired.net/resources/mjm-fedora-f10.html#java

[saric@xbox bin]$ java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Server VM (build 11.0-b16, mixed mode)

Comment 2 Joachim Selke 2009-03-27 16:12:49 UTC
There is a workaround: Setting the environment variable XMODIFIERS to XIM (e.g. by adding "export XMODIFIERS=XIM" to $HOME/.bashrc) makes the problem disappear.

Comment 3 Bug Zapper 2009-11-18 09:41:37 UTC
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2009-12-18 07:18:32 UTC
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.