You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Errors about "is_wayland" Currently installing, can edit this with precise errors afterward.
Description
After doing some digging I discovered that the issue is with this line: output = shell.run_command("loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type | grep wayland", suppress_message=True, return_output=True, run_as_user=username).strip()
It appears that DietPi doesn't include loginctl. I'm able to bypass the check by manually editing the script to hard code it to "x11".
It would be great if I was able to bypass detection, maybe by passing an argument when running the script e.g. sudo -E env PATH=$PATH python3 adafruit-pitft.py --display=35r --display-manager=x11 --rotation=90 --install-type=fbcp
Cheers!
Additional information
No response
The text was updated successfully, but these errors were encountered:
Script Command
sudo -E env PATH=$PATH python3 adafruit-pitft.py --display=35r --rotation=90 --install-type=fbcp
Operating System
32bit DietPi v9.6.1
Hardware
Raspberry Pi Model B Rev 2
Behavior
Errors about "is_wayland" Currently installing, can edit this with precise errors afterward.
Description
After doing some digging I discovered that the issue is with this line:
output = shell.run_command("loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type | grep wayland", suppress_message=True, return_output=True, run_as_user=username).strip()
It appears that DietPi doesn't include
loginctl
. I'm able to bypass the check by manually editing the script to hard code it to "x11".It would be great if I was able to bypass detection, maybe by passing an argument when running the script e.g.
sudo -E env PATH=$PATH python3 adafruit-pitft.py --display=35r --display-manager=x11 --rotation=90 --install-type=fbcp
Cheers!
Additional information
No response
The text was updated successfully, but these errors were encountered: