Did you get the 127 error code too Trinidad? I saw it every time the script crashed when I was initially testing it.
The " '[' 127 -ne 0 ']' " part was being generated from line 786 where "127" was the output of PIPESTATUS(0)
The " '[' 127 -ne 0 ']' " part was being generated from line 786 where "127" was the output of PIPESTATUS(0)
Code:
if [ "${PIPESTATUS[0]}" -ne "0" ]; then _clean_up; exit 0 ; fi # If Quit is clicked then exit
(05-17-2024, 12:14 PM)trinidad link Wrote:Quote:anyway the PIPESTATUS(0) array was being populated with the error code 127
Generally means command not found so usually something is out of wack with the PATH system variable. Only a few things could have caused this, given that the previous 6.6 code worked fine. Policy kit is iterated differently between 6.6 and 7. The polkit.service file path in systemd is slightly different with the full service configuration being written directly in the .service file in 7 but daemonized in 6.6.
Compare between the two.Code:systemctl status polkit
Given that it's a c2 (command) server perhaps Lite Tweaks user has to be added to polkit.service and/or path to User must be iterated differently in Lite Tweaks.
TC