phillipberndt / autorandr

Auto-detect the connected display hardware and load the appropriate X11 setup using xrandr
2.5k stars 123 forks source link

xrandr command not found #301

Open georghimself opened 2 years ago

georghimself commented 2 years ago

Cheers,

im on the latest Archcraft and my autorandr works great with --change. But somehow the hot plugging is not working. so i check the service (see below) im not sure if this is the reason hot plugging doesnt work but i guess so.

autorandr.service - autorandr execution hook Loaded: loaded (/usr/lib/systemd/system/autorandr.service; enabled; preset: disabled) Active: inactive (dead)

Sep 01 10:21:32 neuromancer autorandr[13985]: Running autorandr as jan for display :0 Sep 01 10:21:32 neuromancer systemd[1]: autorandr.service: Deactivated successfully. Sep 01 10:21:32 neuromancer systemd[1]: Finished autorandr execution hook. Sep 01 10:21:42 neuromancer systemd[1]: Starting autorandr execution hook... Sep 01 10:21:42 neuromancer autorandr[14055]: /bin/sh: line 1: xrandr: command not found Sep 01 10:21:42 neuromancer autorandr[14054]: Failed to run xrandr (line 548) Sep 01 10:21:42 neuromancer autorandr[14054]: autorandr running as user xxx (started from batch instance) Sep 01 10:21:42 neuromancer autorandr[14053]: Running autorandr as xxx for display :0 Sep 01 10:21:42 neuromancer systemd[1]: autorandr.service: Deactivated successfully. Sep 01 10:21:42 neuromancer systemd[1]: Finished autorandr execution hook.

phillipberndt commented 2 years ago

Sounds like PATH isn't set up correctly for whatever reasons. Try setting it to include /usr/bin wherever is most appropriate in your setup.

georghimself commented 2 years ago

echo $PATH /usr/share/archcraft/scripts:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/xxx/.config/bspwm/bin

Also i can run xrandr from the shell and autorandr --change does work so it uses the xrandr command right

Thanks for your help @phillipberndt

phillipberndt commented 2 years ago

PATH in your shell isn't necessarily the same as when systemd invokes the command.

georghimself commented 2 years ago

works again after reboot. didnt change anything. i think it could be the suspend