V2.31.0 unable to start

sdetweil

@htilburgs in terminal window no spaces between things…
this is like the windows set var=value (without the set prefix)

WAYLAND_DISPLAY=wayland-x

x is a number from 0 to …

we thought wayand-1 was default

htilburgs

@sdetweil said in V2.31.0 unable to start:

WAYLAND_DISPLAY=wayland-x

In terminal window I typed WAYLAND_DISPLAY=wayland-1
Then I did “env”, nothing changed.
npm run start:wayland still gives the same error.

sdetweil

@htilburgs said in V2.31.0 unable to start:

Then I did “env”, nothing changed.

you should have seen this in the env output

but our code says IF NOT SET, use wayland-1
which looks like an error

so if you set it to the same value it won’t improve

I’d try wayland-0

maybe the wlr_randr command will tell you what it is?

htilburgs

@sdetweil Maybe I don’t understand.
WAYLAND_DISPLAY=wayland-0 still gives wayland-1 in npm run start:wayland.

wlr_randr gives

pi@MagicMirror:~/MagicMirror $ wlr_randr
-bash: wlr_randr: command not found

By the way, my PIR command do work

onCommand: "WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 --on --transform 270 --mode='1920x1080'",

offCommand: "WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 --off",

htilburgs

When I give command

pi@MagicMirror:~ $ WAYLAND_DISPLAY='wayland-1' wlr-randr --output HDMI-A-1 
HDMI-A-1 "Samsung Electric Company SyncMaster 0x00000001 (HDMI-A-1)"
  Physical size: 700x390 mm
  Enabled: yes
  Modes:
    720x400 px, 70.082001 Hz
    640x480 px, 59.939999 Hz
    640x480 px, 60.000000 Hz
    640x480 px, 66.667000 Hz
    640x480 px, 72.808998 Hz
    640x480 px, 75.000000 Hz
    720x480 px, 59.939999 Hz
    720x480 px, 59.939999 Hz
    720x480 px, 60.000000 Hz
    720x480 px, 60.000000 Hz
    720x576 px, 50.000000 Hz
    800x600 px, 60.317001 Hz
    800x600 px, 72.188004 Hz
    800x600 px, 75.000000 Hz
    832x624 px, 74.551003 Hz
    1024x768 px, 60.004002 Hz
    1024x768 px, 70.069000 Hz
    1024x768 px, 75.028999 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 50.000000 Hz
    1280x720 px, 59.939999 Hz
    1280x720 px, 60.000000 Hz
    1280x720 px, 60.000000 Hz
    1152x864 px, 75.000000 Hz
    1280x800 px, 59.910000 Hz
    1440x900 px, 59.901001 Hz
    1280x1024 px, 60.020000 Hz
    1280x1024 px, 75.025002 Hz
    1600x900 px, 60.000000 Hz
    1680x1050 px, 59.882999 Hz
    1920x1080 px, 23.976000 Hz
    1920x1080 px, 24.000000 Hz
    1920x1080 px, 25.000000 Hz
    1920x1080 px, 29.969999 Hz
    1920x1080 px, 30.000000 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 50.000000 Hz
    1920x1080 px, 59.939999 Hz
    1920x1080 px, 60.000000 Hz
    1920x1080 px, 60.000000 Hz (preferred, current)
  Position: 0,0
  Transform: 270
  Scale: 1.000000

sdetweil

@htilburgs so wayland-1 seems to be correct

rkorell

@htilburgs said in V2.31.0 unable to start:

-bash: wlr_randr: command not found

shouldn’t it be wlr-randr ?

Regards,
Ralf

htilburgs

@rkorell
You’re correct, but then I get

rkorell

@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 use

DISPLAY=:0.0

as a hint upfront your terminal command.
At least for xrandr this works and is necessary.

DISPLAY=:0.0 xrandr --output HDMI-1 --off

is my xrandr console equivalent for the “normal” command

xrandr --output HDMI-1 --off

I’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

sdetweil

@rkorell xrandr needs DISPLAY