Bug 770723

Summary:	Menus in Swing applications do not properly receive keyboard input
Product:	[Fedora] Fedora	Reporter:	Michael Ekstrand <michael>
Component:	java-1.7.0-openjdk	Assignee:	Deepak Bhole <dbhole>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	16	CC:	dbhole, jvanek, maxamillion, omajid, otaylor, walters
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 13:44:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Michael Ekstrand 2011-12-28 16:05:34 UTC

Description of problem:
When a menu in a Java Swing application is activated using is access key, its subcommands cannot be selected by their access key.

Version-Release number of selected component (if applicable):
mutter-3.2.1-2.fc16.i686

How reproducible:
Always.

Steps to Reproduce:
1. Start a Java Swing application, like JEdit, IntelliJ IDEA, or NetBeans. LAF does not matter - I observe the problem with Metal, GTK, and IntelliJ's custom LAF.
2. Open a menu by access key (e.g. Alt+F)
3. Press the access key for a menu command (e.g. o for Open)
  
Actual results:
Nothing

Expected results:
The chosen command is activated.

Additional info:
Arrow keys, escape, and enter are properly routed - I can navigate menu options by them.

JRE does not matter - the problem occurs with OpenJDK 1.6, OpenJDK 1.7, and Oracle's JDK 1.7u2 binaries.

The problem also manifests in fallback mode. Therefore, it seems to me that this is either a problem in code shared between Metacity and Mutter, or elsewhere in the graphics stack - possibly something in GTK+ that is interacting badly with AWT. Mutter seemed like the most appropriate starting point for hunting this down.

The problem does not appear on Ubuntu Lucid 64-bit with 64-bit JDK 1.7u2 from Oracle.

Comment 1 Michael Ekstrand 2012-01-01 20:38:22 UTC

This also happens in XFWM, so I'm reasonably confident it is not a mutter or metacity problem. Moving to the OpenJDK package.

Comment 2 Michael Ekstrand 2012-01-11 16:06:17 UTC

It seems to be working correctly now, but I am not sure what change fixed it. I'll keep an eye on it for a bit and poke some more with different JREs.

Comment 3 Fedora End Of Life 2013-01-16 13:05:42 UTC

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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 Fedora End Of Life 2013-02-13 13:44:35 UTC

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.