Yeah the scripts were executables but the services weren’t and I check and the others were. So I set mine with chmod +x. The GPU service was running after that but I’ve been changing the led fix from plain led-fix to led-fix.sh and back an forth. Disabling and enabling the service to make it catch the executable because it was complaining not found with systemctl status led-fix.service
So I moved it to the name it was looking for and that was it.
Led-fix service failed again, I think I need to use autostart. I’m on KDE, should I run it a startup or before sessions startup if I want it to light up for login?
● led-fix.service - Logitech led startup
Loaded: loaded (/etc/systemd/system/led-fix.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Sun 2020-10-11 06:22:04 AST; 4min 32s ago
Process: 626 ExecStart=/usr/bin/led-fix (code=exited, status=2)
Main PID: 626 (code=exited, status=2)
Oct 11 06:22:04 localhost systemd: Starting Logitech led startup...
Oct 11 06:22:04 localhost led-fix: Matching or compatible device not found !
Oct 11 06:22:04 localhost systemd: led-fix.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Oct 11 06:22:04 localhost systemd: led-fix.service: Failed with result 'exit-code'.
Oct 11 06:22:04 localhost systemd: Failed to start Logitech led startup.