#19539 closed defect (othersoftware)
Josm seg faults in Ubuntu 18.04
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Cc: |
Description
I have a fully upto date ubuntu 18.04 OS and have downloaded Josm via synaptic. When I call Josm from the command line I get:
"Using /usr/lib/jvm/java-9-openjdk-amd64/bin/java to execute josm.
2020-07-15 15:30:01.618 INFO: Log level is at INFO (INFO, 800)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fe209171009, pid=31539, tid=31629
#
# JRE version: OpenJDK Runtime Environment (9.0) (build 9-internal+0-2016-04-14-195246.buildd.src)
# Java VM: OpenJDK 64-Bit Server VM (9-internal+0-2016-04-14-195246.buildd.src, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C [libjava.so+0x1d009] JNU_GetEnv+0x19
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /home/XXXXXXXXX/core.31539)
#
# An error report file with more information is saved as:
# /home/XXXXXXXXXX/hs_err_pid31539.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)"
The file hs_err_pid31539.log is attached.
Attachments (1)
Change History (5)
by , 5 years ago
Attachment: | hs_err_pid31539.log added |
---|
comment:1 by , 5 years ago
Replying to coolbears@…:
I have a fully upto date ubuntu 18.04 OS and have downloaded Josm via synaptic. When I call Josm from the command line I get:
"Using /usr/lib/jvm/java-9-openjdk-amd64/bin/java to execute josm.
Either use java-8-openjdk
or java-11-openjdk
. You system is not up to date as Java 9 was removed a long time, ago.
comment:2 by , 5 years ago
Resolution: | → othersoftware |
---|---|
Status: | new → closed |
Segfault is a java issue.
comment:3 by , 5 years ago
Hi
Thank you for a rapid reply. Have upgraded to openjdk 11. Now get the message
No valid JVM found to run JOSM.
The executable /usr/bin/josm which produces this message is riddled with references to java 9.
The message occurs because $JAVACMD is not set. This must be a josm issue.
Cheers
comment:4 by , 5 years ago
You need to contact the packagers of josm for Ubuntu in this case. We're only responsible when you use the packages from our server.
Log file