Opened 14 years ago
Closed 14 years ago
#5762 closed defect (fixed)
Don't work a remote control
Reported by: | anonymous | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Plugin piclayer | Version: | tested |
Keywords: | Cc: |
Description
After upgrading my JOSM to new version (my current version 3731 SVN ru) a remote control don't work
Tested on this http://gis-lab.info/data/mp/josm.htm and this http://yav.gis-lab.info/boundaries/ services
Before upgrading ~2 week ago all be working.
Simptoms:
Popup a error window "It is programm error, call to developer" and noting (if don't run JOSM and try using service - the same reaction). Another function all work.
Attachments (1)
Change History (8)
comment:1 by , 14 years ago
follow-up: 3 comment:2 by , 14 years ago
Replying to anonymous:
Simptoms:
Popup a error window "It is programm error, call to developer"
It should offer an error report. Please add the stack trace (from the error report window or from the console).
and noting (if don't run JOSM and try using service - the same reaction).
I don't understand this, can you explain in more detail or use your native language.
follow-up: 5 comment:3 by , 14 years ago
and noting (if don't run JOSM and try using service - the same reaction).
I don't understand this, can you explain in more detail or use your native language.
Симптомы одинаковы, как с запущенным, так и с незапущенным JOSM: появляется всплывающее окошко с сообщением об ошибке и больше ничего не происходит.
by , 14 years ago
Attachment: | снимок2.png added |
---|
comment:4 by , 14 years ago
Build-Date: 2010-12-17 15:30:56
Revision: 3730
Is-Local-Build: true
Identification: JOSM/1.5 (3730 SVN ru)
Memory Usage: 68 MB / 881 MB (28 MB allocated, but free)
Java version: 1.6.0_20, Sun Microsystems Inc., OpenJDK 64-Bit Server VM
Operating system: Linux
Plugin: DirectUpload
Plugin: buildings_tools
Plugin: download_along
java.lang.reflect.InvocationTargetException
at java.awt.EventQueue.invokeAndWait(EventQueue.java:1000)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:88)
at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:129)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:636)
Caused by: java.lang.IllegalStateException: Dialog was already created
at org.openstreetmap.josm.gui.dialogs.LayerListDialog.createInstance(LayerListDialog.java:88)
at org.openstreetmap.josm.gui.MapFrame.<init>(MapFrame.java:175)
at org.openstreetmap.josm.Main.addLayer(Main.java:239)
at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.finish(DownloadOsmTask.java:157)
at org.openstreetmap.josm.gui.PleaseWaitRunnable$1.run(PleaseWaitRunnable.java:90)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:216)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:602)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:194)
at java.awt.Dialog$1.run(Dialog.java:1072)
at java.awt.Dialog$3.run(Dialog.java:1126)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Dialog.show(Dialog.java:1124)
at java.awt.Component.show(Component.java:1468)
at java.awt.Component.setVisible(Component.java:1420)
at java.awt.Window.setVisible(Window.java:842)
at java.awt.Dialog.setVisible(Dialog.java:1011)
at org.openstreetmap.josm.gui.progress.PleaseWaitProgressMonitor$3.run(PleaseWaitProgressMonitor.java:83)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:602)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)
comment:5 by , 14 years ago
Replying to Alexander Polozov <apolozov@…>:
and noting (if don't run JOSM and try using service - the same reaction).
I don't understand this, can you explain in more detail or use your native language.
Симптомы одинаковы, как с запущенным, так и с незапущенным JOSM: появляется всплывающее окошко с сообщением об ошибке и больше ничего не происходит.
I guess the screenshot is for the case that josm is running. What happens if JOSM isn't running? You are saying, it shows the same message? That sounds very strange to me, where should it come from?
I tested both your urls without any problems. (The stack trace is quite interesting, this shouldn't happen.)
Please try with:
(1) JOSM just started (no data loaded)
(2) some data loaded
and report the results.
comment:6 by , 14 years ago
Yes, if JOSM int't started I see the same message, with the same stack trace. This error independent from loaded or noloaded data. I try both before complaining.
Ah-ha, I did update my JOSM thistime and see its working. Thank :-)
comment:7 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
OS: Gentoo linux x64, browser: Mozilla firefox 4.0beta