Homescreen not always starting on boot
Description
Environment
Activity
Scott Murray April 26, 2019 at 4:33 PM
ATM I believe this is resolved.
Jan-Simon Moeller January 16, 2019 at 12:46 PM
@Scott Murray let's add the weston-ready to master (flounder) in general and adapt the dependencies as proposed. Thanks.
Jacobo Aragunde Pérez January 15, 2019 at 1:25 PM
Hi @Scott Murray, could you share the sources of your weston-ready script? Or are you just launching LayerManagerControl and checking the error output?
Stephane Desneux January 8, 2019 at 1:34 AM
The same could apply to homescreen service too. Not sure. We discovered that doing both helps.
In any case, the wait loop for weston or layer manager to be available should be in the bindings (windowmanager-service and homescreen-service). systemd is not the best way to solve those issues, as "After" or "Requires" are not sufficient to ensure that the required service is available. Introducing some sleeps here and there is even worse.
Nick Yamane January 7, 2019 at 8:34 AM
Hi @Scott Murray, thanks for the detailed explanation. We're gonna check your workaround/script as it seems to be way more robust and unobtrusive.
I agree that would be necessary to have such mechanism at framework level.
There is some undeterministic behavior after rebooting the boards, that results on the homescreen not being shown.It's still unclear to have a fixed way to reproduce the issue, but apparently, it seems to happen more when setting transform=270 to rotate the view.When it's failing the logs show some issues launching the homescreen service.m3ulcb:~# journalctl -r | grep homescreen Jan 03 16:21:54 m3ulcb afbd-homescreen@0.1[3793]: Failed to create display (No such file or directory) Dec 17 11:48:14 m3ulcb systemd[1]: Started This is a demo application for homescreen.