Bug 572147 - JOSM application stops accepting keyboard input
Summary: JOSM application stops accepting keyboard input
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Omair Majid
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-10 12:11 UTC by niklas.laxstrom
Modified: 2010-12-03 17:36 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 17:36:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description niklas.laxstrom 2010-03-10 12:11:57 UTC
Description of problem:
Very often JOSM application stops accepting keyboard input. Sometimes it is only particular dialog, sometimes whole application. I can still interact with mouse.
If I restart ibus-daemon, JOSM crashes, which leads me to believe ibus is somehow related.

Version-Release number of selected component (if applicable):
Any version of JOSM (http://josm.openstreetmap.de/)
-
java version "1.6.0_0"
OpenJDK Runtime Environment (IcedTea6 1.6) (fedora-33.b16.fc12-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
-
Name       : ibus
Arch       : x86_64
Version    : 1.2.0.20100111
Release    : 2.fc12


How reproducible:
Almost always when I use the application for a while.

Steps to Reproduce:
1. Use JOSM
2. Open up a dialog
3. Notice that it doesn't accept keyboard input
4a. If you are lucky, closing the dialog you can still interact with josm
4b. It doesn't take any keyboard input anymore

Expected results:
Keyboard input keeps working.


Additional info:
File earlier a bug to http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=413 but I don't know if it is the correct place. It also contains a backtrace of a crash.

I don't really use any other JAVA applications besides Azureus, with which I have not encountered issue, possible because it does not have much keyboard interaction.

Comment 1 Omair Majid 2010-09-14 16:31:15 UTC
I can not reproduce this problem. Can you please test if this still occurs with the latest version of packages?

java-1.6.0-openjdk-1.6.0.0-42.b18.fc13.x86_64
ibus-1.3.6-1.fc13.x86_64

Comment 2 Bug Zapper 2010-11-03 20:13:26 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 3 Bug Zapper 2010-12-03 17:36:25 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.


Note You need to log in before you can comment on or make changes to this bug.