Either add a "cd ~/KlipperScreen/scripts/" command before the chmod, or use full path to the file.
Attached a snippet from journalctl -u KlipperScreen.service
Log output
Started KlipperScreen.
Running /home/pi/KlipperScreen/scripts/launch_KlipperScreen.sh
/home/pi/KlipperScreen/scripts/KlipperScreen-start.sh: line 7: /home/pi/KlipperScreen/scripts/launch_KlipperScreen.sh: Permission denied
KlipperScreen.service: Main process exited, code=exited, status=126/n/a
KlipperScreen.service: Failed with result 'exit-code'.
KlipperScreen.service: Scheduled restart job, restart counter is at 7.
Stopped KlipperScreen.
What happened?
Following the instructions to configure the service as WIFI on android (https://klipperscreen.readthedocs.io/en/latest/Android/#wifi) and running these commands from the pi user's home directory:
results with an error:
chmod: cannot access 'launch_KlipperScreen.sh': No such file or directory
And the service fails to start.What did you expect to happen instead?
The chmod command should succeed and the service would start.
How to reproduce this bug?
from the home directory, run:
Additional information:
Either add a "cd ~/KlipperScreen/scripts/" command before the chmod, or use full path to the file. Attached a snippet from
journalctl -u KlipperScreen.service
Log output