Hi,
Thank you for your information!
We confirmed this patch then we found this patch is already applied.
So, we changed "/etc/udev/rules.d/71-weston-drm.rules" as below.
We changed from "root" to "test". "test" is our user.
--------------------------------------
ACTION=="add", SUBSYSTEM=="graphics", KERNEL=="fb0", TAG+="systemd", ENV{SYSTEMD_WANTS}+="weston@test.service"
ACTION=="add", SUBSYSTEM=="drm", KERNEL=="card0", TAG+="systemd", ENV{SYSTEMD_WANTS}+="weston@test.service"
--------------------------------------
However, weston cannot start.
--------------------------------------
root@imx8mmevk:~# systemctl status weston@test.service
* weston@test.service - Weston Wayland Compositor (on tty7)
Loaded: loaded (/lib/systemd/system/weston@.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2021-03-25 04:35:35 UTC; 9s ago
Process: 696 ExecStartPre=/usr/bin/chvt 7 (code=exited, status=0/SUCCESS)
Process: 729 ExecStart=/usr/bin/weston --log=${XDG_RUNTIME_DIR}/weston.log $OPTARGS (code=exited, status=1/FAILURE)
Main PID: 729 (code=exited, status=1/FAILURE)
Mar 25 04:35:29 imx8mmevk systemd[1]: Starting Weston Wayland Compositor (on tty7)...
Mar 25 04:35:29 imx8mmevk systemd[1]: Started Weston Wayland Compositor (on tty7).
Mar 25 04:35:35 imx8mmevk systemd[1]: weston@test.service: Main process exited, code=exited, status=1/FAILURE
Mar 25 04:35:35 imx8mmevk systemd[1]: weston@test.service: Failed with result 'exit-code'.
--------------------------------------
Is Our procedure incorrect?
Could you please let us know how to change weston user?
BR