Cluster-gauges (QtWaylandCompositor) start fail

Close for Halibut 8.0.1 release

I believe all the changes to fix this have been merged.

I'm looking into this, there are some configuration tweaks needed for the running applications as non-root change in Halibut that have been tied to weston-ini in meta-agl-profile-graphical, so they're missing when building without weston.  I think I'm close to a fix.

Hi Scott

Thank you for your mention.  We have added the display permission to it's config.xml file as bellow( same as apps/agl-cluster-demo-dashboard's config.xml file) 

---------
<feature name="urn:AGL:widget:required-permission">
    <param name="urn:AGL:permission::public:display" value="required" />              =====> here
    <param name="urn:AGL:permission::system:run-by-default" value="required" />
    <param name="urn:AGL:permission::public:no-htdocs" value="required" />
  </feature>
--------

But it seems not enough because apps/agl-cluster-demo-gauges may need the permission as weston because it will access the bellow resource.

    /dev/dri/card0

    /dev/input/event0

    /dev/input/event1

    /dev/input/event2  etc.

So I think there are two methods to resolve this problem

Method 1: make the agl-cluster-demo-gauges's user to display.

                  weston sets user and group to display in the config file /lib/systemd/system/weston.service 

                 As a AGL application, can we set  agl-cluster-demo-gauges's user to display? (which configure file can set the user?)

Method2: add smack rules

                 we should add rules to access /dev reources, we also can consult the rules added by weston.

                The file's do_install_append (file: ../meta-agl/meta-agl-profile-graphical/recipes-graphics/wayland/weston-init.bbappend)

                But it's not enough, we also need to modify the user attribute of /dev/input   from input to display.

                However,  I can not grasp all the effects  of the user attribute change, 

Can you give me your opinion?

I think I mentioned in our meeting at ALS that the cluster-gauges application needs the new display permission added to its config.xml.  Not having that causes the problem you're seeing.  See:

https://docs.automotivelinux.org/docs/en/master/apis_services/reference/af-main/3-permissions.html#example-of-permissions