Opened 10 years ago
Last modified 9 years ago
#12022 closed defect
display of names/tags mixed up when selecting — at Version 6
| Reported by: | malenki | Owned by: | team |
|---|---|---|---|
| Priority: | critical | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | java8 linux debian ubuntu mint openjdk gnome atk accessibility | Cc: | naoliv, *Martin*, GerdP, sebastic, h4ck3rm1k3, alexkemp |
Description (last modified by )
Please watch the attached video (2MB), the issue is quite hard to explain:
When having selected data and then clicking on one or some objects in the selections window, way ID, node ID, version etc. are shown. That is not bad, but when selecting several items in the window, the same ID is shown on different places.
This also works for marking some of the tags of one (or more) selected object. This is more irritating than the behaviour mentioned before, but sometimes harder to reproduce.
OSM data is not altered by this behaviour.
This only happens on Java 1.8 – the version used is
openjdk version "1.8.0_66-internal" OpenJDK Runtime Environment (build 1.8.0_66-internal-b01) OpenJDK 64-Bit Server VM (build 25.66-b01, mixed mode)
I used a blank ~/.josm on Linux LMDE 2 Betsy
Tested with r8964, the issue shows also up with r7499, older versions I didn't test.
Change History (7)
by , 10 years ago
comment:1 by , 10 years ago
| Description: | modified (diff) |
|---|---|
| Summary: | names/tags mixed up when selecting → display of names/tags mixed up when selecting |
| Version: | → latest |
comment:2 by , 10 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 10 years ago
| Keywords: | java8 linux added; java_8 removed |
|---|
follow-up: 5 comment:4 by , 10 years ago
it looks like the same problem than #11920. Can you please test with Java 7 and see if the result if the same?
I need your status report including command line options please.
comment:5 by , 10 years ago
Replying to Don-vip:
it looks like the same problem than #11920.
I looked for several keywords I could think of but obviously didn't find this ticket.
Can you please test with Java 7 and see if the result if the same?
As I said the issue appears only with Java 8. This means it doesn't with Java 7.
I need your status report including command line options please.
Usually I run JOSM with this auto update script which uses this line to start JOSM: ($useopengl is empty):
aoss java -jar -Xmx14000 -Dsun.java2d.opengl=$useopengl $jarfile $@ >~/.josm/josm.log 2>&1 &
The older version I invoked with just java -jar $file
Report:
Revision: 8964 Repository Root: http://josm.openstreetmap.de/svn Relative URL: ^/trunk Last Changed Author: simon04 Last Changed Date: 2015-10-27 23:40:20 +0100 (Tue, 27 Oct 2015) Build-Date: 2015-10-28 02:32:10 URL: http://josm.openstreetmap.de/svn/trunk Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last Changed Rev: 8964 Identification: JOSM/1.5 (8964 de) Linux LMDE 2 Betsy Memory Usage: 664 MB / 2222 MB (494 MB allocated, but free) Java version: 1.8.0_66-internal, Oracle Corporation, OpenJDK 64-Bit Server VM VM arguments: [-Dsun.java2d.opengl=false] Dataset consistency test: No problems found Plugins: - FastDraw (31694) - FixAddresses (31694) - HouseNumberTaggingTool (31603) - ImportImagePlugin (31603) - InfoMode (31603) - Mapillary (31694) - OpeningHoursEditor (31696) - PicLayer (31694) - RoadSigns (31694) - ShapeTools (1000) - apache-commons (31718) - apache-http (31687) - buildings_tools (31694) - conflation (0.1.8) - contourmerge (1013) - download_along (31603) - editgpx (31603) - ext_tools (31603) - fieldpapers (v0.4.0) - geotools (31603) - imagery_offset_db (31694) - jts (31603) - log4j (31603) - mapdust (31694) - measurement (31694) - photo_geotagging (31694) - photoadjust (31694) - reltoolbox (31694) - reverter (31694) - tag2link (31603) - tageditor (31615) - terracer (31694) - todo (29154) - turnrestrictions (31694) - undelete (31603) - utilsplugin2 (31694) - waydownloader (31603) - wikipedia (31694) Last errors/warnings: - W: Cannot lock cache directory. Will not use disk cache - W: Cannot start IPv4 remotecontrol server on port 8111: Die Adresse wird bereits verwendet - W: Cannot start IPv6 remotecontrol server on port 8111: Die Adresse wird bereits verwendet - W: Cannot start IPv4 remotecontrol https server on port 8112: Die Adresse wird bereits verwendet - W: Cannot start IPv6 remotecontrol https server on port 8112: Die Adresse wird bereits verwendet
comment:6 by , 10 years ago
| Description: | modified (diff) |
|---|



Video of tags and names of selected objects getting mixed up