GitLab

I have weston 9.0 running with kiosk-shell on an i.MX arm board with two HDMI displays. I am trying to get two chromium ozone wayland windows to open, one on each screen, but they both seem to always open on the same screen. My test case is to run weston with the following weston.ini:

[core]
shell=kiosk-shell.so
idle-time=0

[shell]

[output]
name=HDMI-A-1
mode=1920x1080@60
app-ids=Chrome-testa

[output]
name=HDMI-A-2
mode=1920x1080@60
app-ids=Chrome-testb

I run:

export CHROME_DESKTOP=Chrome-testa.desktop
chromium --use-gl=egl --no-first-run --incognito --ozone-platform=wayland --user-data-dir=chrome-testa --in-process-gpu https://google.com

and then:

export CHROME_DESKTOP=Chrome-testb.desktop
chromium --use-gl=egl --no-first-run --incognito --ozone-platform=wayland --user-data-dir=chrome-testb --in-process-gpu https://cnn.com

weston-debug proto shows:

[2021-02-10 12:18:01.243][proto] client 0xaaaaffdbd6d0 rq xdg_toplevel@24.set_app_id("Chrome-testa")

for the first chromium, and:

[2021-02-10 12:19:41.768][proto] client 0xaaaaffdbd030 rq xdg_toplevel@24.set_app_id("Chrome-testb")

for the second chromium, but they both show up on the same output. If I move the mouse cursor over to the other screen before starting the second chromium process then they show up on different screens, but trying to start them from systemd.

Logs: scene.log

testa.log

testb.log