(Ubuntu 20.04) After starting JSOM via Terminal, the process in the terminal doesn't stop. If it's terminated, JOSM closes and can only be re-opened via Terminal.

[anonymous]

What steps will reproduce the problem?

1. start JOSM via Terminal: "cd ~/Desktop" then "javaws josm.jnlp" (with the .jnlp on Desktop)
2. wait for JOSM to be set up
3. close Terminal, ignore running process warning

What is the expected result?

I kinda need the Terminal while using JOSM. JOSM shouldn't close when I close the Terminal.

What happens instead?

Can't use the Terminal without force-closing JOSM.

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

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2022-08-01 20:38:58 +0200 (Mon, 01 Aug 2022)
Revision:18531
Build-Date:2022-08-02 01:30:56
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (18531 en_GB) Linux Ubuntu 20.04.4 LTS
Memory Usage: 320 MB / 3474 MB (237 MB allocated, but free)
Java version: 11.0.15+10-LTS, Azul Systems, Inc., OpenJDK 64-Bit Server VM
Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel
Screen: :0.0 1920×1080 (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→16×16, 32×32→32×32
Environment variable LANG: en_GB.UTF-8
System property file.encoding: UTF-8
System property sun.jnu.encoding: UTF-8
Locale info: en_GB
Numbers with default locale: 1234567890 -> 1234567890
Desktop environment: ubuntu:GNOME
fonts-noto: fonts-noto:-
VM arguments: [-Dicedtea-web.bin.location=/opt/OpenWebStart/javaws, -Djava.util.Arrays.useLegacyMergeSort=true, --add-exports=jdk.deploy/com.sun.deploy.config=ALL-UNNAMED, --add-opens=java.desktop/javax.swing.text.html=ALL-UNNAMED, --add-reads=java.naming=ALL-UNNAMED,java.desktop, --add-exports=java.base/sun.security.action=ALL-UNNAMED,java.desktop, --add-reads=java.base=ALL-UNNAMED,java.desktop, --add-exports=java.naming/com.sun.jndi.toolkit.url=ALL-UNNAMED,java.desktop, --add-opens=java.base/jdk.internal.loader=ALL-UNNAMED, --add-exports=java.desktop/com.apple.eawt=ALL-UNNAMED, --add-exports=java.desktop/sun.awt=ALL-UNNAMED,java.desktop, --add-opens=java.base/jdk.internal.ref=ALL-UNNAMED, --add-exports=java.base/sun.security.validator=ALL-UNNAMED,java.desktop, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.base/sun.net.www.protocol.jar=ALL-UNNAMED,java.desktop, --add-exports=java.base/jdk.internal.util.jar=ALL-UNNAMED,java.desktop, --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED, --add-exports=java.base/com.sun.net.ssl.internal.ssl=ALL-UNNAMED,java.desktop, --add-exports=javafx.graphics/com.sun.javafx.application=ALL-UNNAMED, --add-modules=java.scripting,java.sql,javafx.controls,javafx.media,javafx.swing,javafx.web, --add-exports=java.desktop/sun.awt.X11=ALL-UNNAMED,java.desktop, --add-exports=java.desktop/sun.applet=ALL-UNNAMED,java.desktop,jdk.jsobject, --add-exports=java.base/sun.net.www.protocol.http=ALL-UNNAMED,java.desktop, --add-opens=java.base/java.lang=ALL-UNNAMED, --add-exports=java.base/sun.security.util=ALL-UNNAMED,java.desktop, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, --add-reads=java.desktop=ALL-UNNAMED,java.naming, --add-opens=java.base/java.nio=ALL-UNNAMED, --add-exports=java.base/sun.security.x509=ALL-UNNAMED,java.desktop, --add-opens=java.desktop/javax.imageio.spi=ALL-UNNAMED, --add-exports=java.desktop/javax.jnlp=ALL-UNNAMED,java.desktop, --add-exports=java.base/sun.security.provider=ALL-UNNAMED,java.desktop]

[GerdP]

You can either start a new terminal or don't start JOSM from that terminal. I think that's normal. Where's the problem?

[taylor.smock]

I'm kind of annoyed when a process detaches itself from the terminal. Which is what this ticket is advocating for. Doing so breaks various expectations, and should never be done lightly or (IMO) by default.

@anonymous: If you really want that behavior, add nohup at the front and & at the end. So cd ~/Desktop && nohup javaws josm.jnlp &. At that point, closing the terminal won't close JOSM. It may still complain about killing Java, but in my testing it didn't kill JOSM (note: testing was on mac, so test on your system).

Identification: JOSM/1.5 (18531 en_GB) Linux Ubuntu 20.04.4 LTS

We have an Ubuntu repository that you can use. So you don't have to start JOSM via the terminal, which will also fix this problem. If you don't want to add a repository, there are flatpak/snap packages available. The snap is largely unmaintained (see log/josm/trunk/native/snapcraft.yaml, last modified 5 years ago), and really could use some updates for the current snapcraft state.