User interface unresponsive and exceptions

[dtimms@…]

What steps will reproduce the problem?

1. on fedora 12 x86_64, yum install josm
2. josm from desktop menus in gnome
3. open, choose a gpx file
4. wait a little
5. tried Download from OSM

What is the expected result?

1:

Installed:

josm.noarch 0:0-0.10.3514svn.fc12

Dependency Installed:

ant.x86_64 0:1.7.1-13.fc12
metadata-extractor.noarch 0:2.3.1-5.fc12
xerces-j2.x86_64 0:2.7.1-12.3.fc12.1
xml-commons-resolver.x86_64 0:1.1-4.16.fc12

$ java -version
java version "1.6.0_18"
OpenJDK Runtime Environment (IcedTea6 1.8.1) (fedora-40.b18.fc12-x86_64)
OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)

2: ui shows
3: open dialog shows and accepts input.
4: dialog closes, but nothing seemed to happen for at least five seconds in the UI.
5: about the same time got the exception.

I haven't run josm before.

What happens instead?
The null exception trace

Please provide any additional information below. Attach a screenshot if possible.

Revision: 3514
Build-Date: 2010-09-07 20:29:59
Is-Local-Build: true

Identification: JOSM/1.5 (3514 SVN en_AU)
Memory Usage: 83 MB / 8796093022207 MB (27 MB allocated, but free)
Java version: 1.5.0, Free Software Foundation, Inc., GNU libgcj
Operating system: Linux

java.lang.NullPointerException

at org.openstreetmap.josm.gui.progress.PleaseWaitProgressMonitor.close(PleaseWaitProgressMonitor.java:151)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:99)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:129)
at java.util.concurrent.Executors$RunnableAdapter.call(libgcj.so.10)
at java.util.concurrent.FutureTask$Sync.innerRun(libgcj.so.10)
at java.util.concurrent.FutureTask.run(libgcj.so.10)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(libgcj.so.10)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(libgcj.so.10)
at java.lang.Thread.run(libgcj.so.10)

=====
Note at startup, JOSM requires java v6, detected java v1.5.0, even though the java is 1.6 (iced tea).

[dtimms@…]

exceptions from the command line

[bastiK]

As you can see from the bug report, JOSM is run with GNU libgcj which does not work at the moment.
Somehow the startup script manages to run the wrong java although you have openjdk in your path. As a workaround you can start JOSM as

java -jar /PATH/TO/josm.jar

Please also report the bug to your distributor.