Skip to:
On next (not tested on master but...) the application homescreen doesn't start around one time for two trial with the message:
systemd[1]: afm-appli-homescreen--0.1--main@1001.service: Bound to unit afm-api-vshl-core@1001.service, but unit isn't active.
Close for JJ RC1
Yes, the review is for master and it is safe.
From last dev meeting, the branch next is going to be merged with master very soon.
So I guess this is safe to be pushed into master as well?
After some test, putting Requires instead of BindsTo solves the issue on next/zeus.
But it also reveal an other issue: https://lf-automotivelinux.atlassian.net/browse/SPEC-3184#icft=SPEC-3184.
After replacing BindsTo by Requires, I do not see the issue anymore.
But the launcher sometime does not display any icon.
On next (not tested on master but...) the application homescreen doesn't start around one time for two trial with the message:
systemd[1]: afm-appli-homescreen--0.1--main@1001.service: Bound to unit afm-api-vshl-core@1001.service, but unit isn't active.