When displaying ivi-application surfaces, these surfaces are shown correctly, only when there is just 1 layer in the ivi-shell.

display-image -id 1
LayerManagerControl create layer 1 100 100
LayerManagerControl set layer 1 visibility 1
LayerManagerControl set surface 1 visibility 1
LayerManagerControl set layer 1 render order 1
LayerManagerControl set screen 0 render order 1
# surface is visible and can be toggled:
LayerManagerControl set surface 1 visibility 0
LayerManagerControl set surface 1 visibility 1
# add another layer
LayerManagerControl create layer 2 100 100
# from this point on, the surface will not update anymore

After the second layer is created - not even added to the screen render order or set to be visible - the surface will no longer reflect what is on screen. If it was invisible before the second layer was created, it will now be visible, but cannot be switched to invisible.

Interestingly, the properties of the objects involved - namely the ivi_controller_surface and the layers, will all reflect the properties given to them by the controller, but the display will not show it correctly.

This issue has another severe side effect; when surfaces first appear in a scene with multiple layers, the surface will never get a first wl_surface::enter (signalling that is is now on the corresponding output), which means, the surface will not render.