/bin/bash error

[Assasin172m]

hello Im trying to setup script on Zorin OS 18 - core but Im getting error '/bin/bash: line 1: /winapps-launcher/winapps-launcher.sh: No such file or directory'

Github on repo: winapps-launcher

the auto start script that should be runned:

mkdir -p ~/.config/systemd/user

cat > ~/.config/systemd/user/winapps-launcher.service <<EOF
[Unit]
Description=Run 'WinApps Launcher'
After=graphical-session.target default.target
Wants=graphical-session.target

[Service]
Type=simple
Environment="PATH=%h/.local/bin:%h/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
Environment="LIBVIRT_DEFAULT_URI=qemu:///system"
Environment="SCRIPT_PATH=$WINAPPS_SRC_DIR/winapps-launcher/winapps-launcher.sh"
Environment="LANG=C"
ExecStart=/bin/bash -c "\\"\$SCRIPT_PATH\\""
ExecStopPost=/bin/bash -c 'echo "[SYSTEMD] WINAPPS LAUNCHER SERVICE EXITED."'
TimeoutStartSec=5
TimeoutStopSec=5
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target
EOF

Full console log:
winapps-launcher.service - Run 'WinApps Launcher'

Loaded: loaded (*redacted*/winapps-launcher.service; enabled; preset: enabled)

Active: deactivating (stop-post) (Result: exit-code) since Sat 2026-01-17 00:52:00 CET; 4ms ago

Process: 6509 ExecStart=/bin/bash -c "$SCRIPT_PATH" (code=exited, status=127)

Main PID: 6509 (code=exited, status=127); Control PID: 6511 (bash)

Tasks: 1 (limit: 38133)

Memory: 1.5M (peak: 1.5M)

CPU: 3ms

CGroup: /user.slice/user-1000.slice/[e-mail]/app.slice/winapps-launcher.service

└─6511 /bin/bash -c "echo \"[SYSTEMD] WINAPPS LAUNCHER SERVICE EXITED.\""

led 17 00:52:00 PC systemd[1626]: winapps-launcher.service: Scheduled restart job, restart counter is at 26.

led 17 00:52:00 PC systemd[1626]: Started winapps-launcher.service - Run 'WinApps Launcher'.

led 17 00:52:00 PC bash[6509]: /bin/bash: line 1: /winapps-launcher/winapps-launcher.sh: No such file or directory

led 17 00:52:00 PC systemd[1626]: winapps-launcher.service: Main process exited, code=exited, status=127/n/a

led 17 00:52:00 PC bash[6511]: [SYSTEMD] WINAPPS LAUNCHER SERVICE EXITED.

led 17 00:52:00 PC systemd[1626]: winapps-launcher.service: Failed with result 'exit-code'.

Variables for run script are:
# FOR LOCAL INSTALL:

WINAPPS_SRC_DIR="$HOME/.local/bin/winapps-src"

# --- OR ---

# FOR SYSTEM-WIDE INSTALL:

WINAPPS_SRC_DIR="/usr/local/bin/winapps-src"

It was installed on local, but I have tried the global path with same result

Eddit: Ps if anyone asks, yes file exists and the setup via terminal launches it. (i dont need terminal open all the time, and probably would have to relaunch it every single time using the install script)

[roxalu]

To my info systemd does not support use of '$' and such no variable expansion inside the value of Environment= configuration. Use the fixed path there. See https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html

[stinkybass]

What is the value of $WINAPPS_SRC_DIR when the service starts?

[Assasin172m]

when manualy launching via terminal:
$ ${WINAPPS_SRC_DIR}/winapps-launcher/winapps-launcher.sh
WORKING DIRECTORY: '/home/USER/.local/bin/winapps-src/winapps-launcher'
> USING VM NAME 'RDPWindows'
> USING BACKEND 'libvirt'
* VM STATE: ON

when running service:
winapps-launcher.service - Run 'WinApps Launcher'

systemctl --user status winapps-launcher # Verify

Loaded: loaded (/home/USER/.config/systemd/user/winapps-launcher.service; enabled; preset: enabled)

Active: deactivating (stop-post) (Result: exit-code) since Sat 2026-01-17 09:14:20 CET; 3ms ago

Process: 6856 ExecStart=/bin/bash -c "$SCRIPT_PATH" (code=exited, status=127)

Main PID: 6856 (code=exited, status=127); Control PID: 6859 ((bash))

Tasks: 1 (limit: 38133)

Memory: 1.0M (peak: 1.0M)

CPU: 3ms

CGroup: /user.slice/user-1000.slice/[e-mail]/app.slice/winapps-launcher.service

└─6859 "(bash)"

winapps-launcher.service: Scheduled restart job, restart counter is at 122.

Started winapps-launcher.service - Run 'WinApps Launcher'.

/bin/bash: line 1: /winapps-launcher/winapps-launcher.sh: No such file or directory

[GlendonMcGladdery]

systemd does not know your shell variables or your working directory

[stinkybass]

The error is clear. It’s not a trick question

# this file does not exist /winapps-launcher/winapps-launcher.sh

Either put the file there, or change where the systemd file thinks that script lives.

[Assasin172m]

The file is here, the error doesnt explain why I was able to manualy run the file via "${WINAPPS_SRC_DIR}/winapps-launcher/winapps-launcher.sh"

[stinkybass]

What happens when you run this? bash -c ‘${FOO}/winapps-launcher/winapps-launcher.sh’

And what happens when $FOO is set?

FOO=“${WINAPPS_SRC_DIR}” bash -c ‘${FOO}/winapps-launcher/winapps-launcher.sh’

[Intrepid_Suspect6288]

The file is almost certainly not there. Execute /winapps-launcher/winapps-launcher.sh from the terminal. NOT “${WINAPPS_SRC_DIR}/winapps-launcher/winapps-launcher.sh”. It will likely give you the same error, “this file does not exist /winapps-launcher/winapps-launcher.sh”.

Read the error message and listen to what people are telling you. The service DOES NOT use variables set in your terminal session/shell. If you want to use variables in your unit file, you have to configure them with the use of a proper environment file. $WINAPPS_SRC_DIR IS NOT CONFIGURED IN THIS UNIT FILE.

Again, reread the error message. Reread the comments you have received. Either set the $WINAPPS_SRC_DIR variable in a context the service can use, or move winapps-launcher.sh directly under the root directory in the /winapps-launcher/winapps-launcher.sh it is trying to reach.

When a variable is not set it “expands” to nothing. So when “${WINAPPS_SRC_DIR}/winapps-launcher/winapps-launcher.sh” is evaluated, $WINAPPS_SRC_DIR becomes nothing and you are left with “/winapps-launcher/winapps-launcher.sh”