I have a personal Conky script (at
~/.conky/conky-launch.sh
) that I'd like to execute every time I boot up my OS (which is Fedora Workstation 39). So, I created a systemd
service file named personal-conky.service
as follows:
[Unit]
Description=Opens up my personal conky setup on boot
[Service]
User=arch
ExecStart=/home/arch/.conky/conky-launch.sh
[Install]
WantedBy=multi-user.target
Next, I enabled the service by doing:
$ sudo systemctl enable personal-conky.service
When I rebooted however I found that the script has not executed. When I did:
$ systemctl status personal-conky.service
I got the following error:
× personal-conky.service - Opens up my personal conky setup on boot
Loaded: loaded (/etc/systemd/system/personal-conky.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: failed (Result: exit-code) since Wed 2024-01-31 20:12:57 IST; 4s ago
Duration: 3ms
Process: 5602 ExecStart=/home/arch/.conky/conky-launch.sh (code=exited, status=203/EXEC)
Main PID: 5602 (code=exited, status=203/EXEC)
CPU: 1ms
Jan 31 20:12:57 fedora systemd: Started personal-conky.service - Opens up my personal conky setup on boot.
Jan 31 20:12:57 fedora (aunch.sh): personal-conky.service: Failed to locate executable /home/arch/.conky/conky-launch.sh: Permission denied
Jan 31 20:12:57 fedora (aunch.sh): personal-conky.service: Failed at step EXEC spawning /home/arch/.conky/conky-launch.sh: Permission denied
Jan 31 20:12:57 fedora systemd: personal-conky.service: Main process exited, code=exited, status=203/EXEC
Jan 31 20:12:57 fedora systemd: personal-conky.service: Failed with result 'exit-code'.
Why is this happening, and what should I do to fix this?
Asked by archie
(131 rep)
Jan 31, 2024, 02:45 PM
Last activity: Jan 31, 2024, 04:22 PM
Last activity: Jan 31, 2024, 04:22 PM