id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22088	[RFC PATCH] Debian start script does not properly check if a path does not exist or is not executable	taylor.smock	team	"I've been working on getting downstreams to use our start script (with some ''minor'' patches) to hopefully avoid future issues where we get bug reports that we've fixed in the start script.

Steps to reproduce (on Debian/Ubuntu):
1. If `/usr/lib/jvm/default-java/bin/java` exists, move it (example: `mv /usr/lib/jvm/default-java/bin/java /usr/lib/jvm/default-java/bin/java.bak`)
2. Attempt to run the start script
3. If you moved `/usr/lib/jvm/default-java/bin/java` in step 1, move it back (example: `mv /usr/lib/jvm/default-java/bin/java.bak /usr/lib/jvm/default-java/bin/java`)

You may also be able to reproduce by unsetting `JAVA_HOME` or setting it to an empty string (e.g., `JOSM_HOME="""" ./josm`)

From https://github.com/flathub/org.openstreetmap.josm/issues/55,
{{{
➜  ~ flatpak install flathub org.openstreetmap.josm                                                       
Looking for matches…

org.openstreetmap.josm permissions:
    ipc   network   x11   file access [1]

    [1] xdg-download


        ID                              Branch          Op          Remote          Download
 1. [✓] org.openstreetmap.josm          stable          i           flathub         78.5 MB / 76.9 MB

Installation complete.
➜  ~ flatpak run org.openstreetmap.josm
which: no dpkg in (/usr/bin:/app/bin:/app/jre/bin)
Using /usr/lib/jvm/default-java/bin/java to execute josm.
/app/bin/josm: line 91: /usr/lib/jvm/default-java/bin/java: No such file or directory
}}}

This is due to source:trunk/native/linux/tested/usr/bin/josm@18297:33,41-57#L33"	defect	closed	normal	22.06	Core		fixed	linux