Modify ↓
Opened 8 years ago
Closed 8 years ago
#15999 closed defect (duplicate)
coding error after updating JOSM
| Reported by: | anonymous | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Running an old OSM version
- Updating OSM without shutting dozn the old OSM running version
- Starting the new updated OSM version
What is the expected result?
Normal starting of updated JOSM
What happens instead?
Normal starting of updated JOSM plus a bug window saying there is a coding error
Please provide any additional information below. Attach a screenshot if possible.
URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-01-28 23:08:56 +0100 (Sun, 28 Jan 2018)
Build-Date:2018-01-28 22:25:44
Revision:13367
Relative:URL: ^/trunk
Identification: JOSM/1.5 (13367 fr) Linux Ubuntu 14.04.5 LTS
Memory Usage: 166 MB / 789 MB (120 MB allocated, but free)
Java version: 1.8.0_161-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: :0.0 1600x900
Maximum Screen Size: 1600x900
VM arguments: [-Djava.security.policy=file:${JAVA_HOME}/jre/lib/security/javaws.policy, -DtrustProxy=true, -Djnlpx.home=${JAVA_HOME}/jre/bin, -Djava.security.manager, -Djnlpx.origFilenameArg=${HOME}/.java/deployment/cache/6.0/56/1ee8cfb8-6ba3b9c8, -Djnlpx.remove=false, -Dsun.awt.warmup=true, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=55662, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp, -Djnlpx.jvm=${JAVA_HOME}/jre/bin/java]
Last errors/warnings:
- E: Handled by bug report queue: java.lang.SecurityException: Impossible de vérifier le fichier JAR de package de sécurité
=== REPORTED CRASH DATA ===
BugReportExceptionHandler#handleException:
No data collected.
Warning issued by: BugReportExceptionHandler#handleException
=== STACK TRACE ===
Thread: Thread-19 (54)
java.lang.SecurityException: Impossible de vérifier le fichier JAR de package de sécurité
at com.sun.deploy.util.SecurityBaseline.verifyJar(Unknown Source)
at com.sun.deploy.util.SecurityBaseline.access$200(Unknown Source)
at com.sun.deploy.util.SecurityBaseline$1.run(Unknown Source)
at java.lang.Thread.run(Thread.java:748)
Attachments (1)
Change History (2)
by , 8 years ago
| Attachment: | Capture du 2018-02-21 22:51:17.png added |
|---|
comment:1 by , 8 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.



Closed as duplicate of #15785.