Read the statement by Michael Teeuw here.
V2.31.0 unable to start
- 
@htilburgs said in V2.31.0 unable to start:
-bash: wlr_randr: command not found
shouldn’t it be wlr-randr ?
Regards,
Ralf - 
@rkorell
You’re correct, but then I get
 - 
@htilburgs :-)
this is correct on console window.
console didn’t know about display unless you’re telling him what display to use.
As far as I know you can useDISPLAY=:0.0as a hint upfront your terminal command.
At least for xrandr this works and is necessary.DISPLAY=:0.0 xrandr --output HDMI-1 --offis my xrandr console equivalent for the “normal” command
xrandr --output HDMI-1 --offI’m not THAT sure if this is true for wlr-randr .
(Because wlr-randr do have this environment variable “WAYLAND_DISPLAY” which is not the case for xrandr…)HTH & regards,
Ralf - 
@rkorell xrandr needs DISPLAY
 - 
@sdetweil yes :-)
 - 
@rkorell oops, never can remember when i need to use underscore vs dash! thanks for the catch!
 
