segfault in agl-compositor with agl-cluster-demo-platform-flutter

Alright, thanks a lot. I've opened https://lf-automotivelinux.atlassian.net/browse/SPEC-4693 for further following in the ini/image configuration mix-up.

  I have now tested with the latest needlefish branch with HEAD at needlefish/14.0.3, and I can confirm the segfault is not seen anymore, the dashboard is working as expected.

> With respect to the fragments, having upstream support to drop e.g. a display stanza like remote-output on to seems like it'd be useful in general.

Sure, and with it more of an argument to look into .

From what I recall in my testing it was having the remote-output configuration in the cluster that was an issue, and realistically it shouldn't be in there since the cluster is acting as a receiver.  With respect to the fragments, having upstream support to drop e.g. a display stanza like remote-output on to seems like it'd be useful in general.  I'm not that keen on moving towards some form of tool to assemble weston.ini at boot time that we'd maintain ourselves.

> try editing weston.ini on the cluster to remove it

You mean on the agl-image-flutter-runtimedebug image, because on cluster it works just fine. (The original jira was the other way around but I can't seem to trigger that crash anymore).

> It'd be quite useful if the libweston configuration stuff could process fragments in a e.g. weston.ini.d/ directory, but it's never been too clear to me if upstream would be interested in the complexity if we did some work to contribute it.

You mean stitching a full config init from multiple bits? The stuff we have in libweston is all hand written, without any deps so I'm not sure how fun would that be..... I'll sure ask for this one. Maybe there's something we can do switch to some helper library like toml (though not sure it would be capable of doing that). I guess the question we'd get here is why not using a tool that that can combine those bits, and provide that to the compositor?