It looks like there is a bug in the core snap on the rPi3 when using the Edge build and also now the beta build. It has stopped serving up the mir-kiosk-apps snap. No Denials in journalctl just the error message
[QPA] QMirClientClientIntegration: connection to Mir server failed.
Mir returned: “”
Happy to help debug by providing files/logs or anything else needed
This sounds more like an incompatibility between the way the server (mir-kiosk) and client (mir-kiosk-apps) are configured. I’m not aware of any updates to either of these recently.
Trying to install the three snaps i get a properly starting mir-kiosk (got a black screen and movable cursor on screen) which indicates that on the image level (core snap, GLES setup etc) everything is ok.
That said … i can actually confirm that the mir-kiosk-apps snap does not start and that i see the same errors in journalctl here …
http://paste.ubuntu.com/24592960/ has the full log output …
something seems out of sync between the apps and the lib/server snap (since the server works fine standalone).
and trying starting the application again (note if you refresh, remove/install, reboot or restart snapd, this policy will be updated and that change will be gone). I suspect your snap will still fail.
Agreed, i think the issue is in the next lines in the logs where it can not find its lib:
May 17 14:22:02 pi3 snap[12051]: Loading module: 'libubuntu_application_api_desktop_mirclient.so.3.0.0' May 17 14:22:02 pi3 snap[12051]: Unable to load selected module, using dummy. May 17 14:22:02 pi3 snap[12051]: Loading module: 'libubuntu_application_api_test.so.3.0.0' May 17 14:22:02 pi3 snap[12051]: [QPA] QMirClientClientIntegration: connection to Mir server failed. May 17 14:22:02 pi3 snap[12051]: Mir returned: "" May 17 14:22:02 pi3 snap[12051]: /snap/mir-kiosk-apps/16/bin/mir-kiosk-app-daemon: line 93: 12066 Terminated
If it doesn’t fail, it still may be the timing issue @ogra mentioned and nothing to do with the apparmor denials (we could determine if that is the case by removing the rules, reloading the profile and then restarting and seeing if it starts to fail again).
In the past when I was looking at mir-kiosk, I needed to do this:
make sure your snap plugs mir and the mir-libs content
install mir kiosk snap
install mir-libs
install the application
make sure that ‘snap interfaces’ shows that the application is connected to both mir and the mir-libs content. If not, connect the interfaces with snap connect
start the application
An additional thing that may be in play is the persistent mount namespace that may not have the mir-libs mounted in your snap’s are like it is supposed to. You can stop your application, run sudo /usr/lib/snapd/snap-discard-ns mir-kiosk-apps and then try again (or make this step ‘4.5’, above).
If this works, please give the output of snap version. I know @zyga-snapd was working on this issue and he may be able to comment further.
Thanks, yes I can confirm the snap is connected to mir and mir-libs. I have just tried your steps just in case but still get the same results.
We have had this working for a couple of months as we use the app as a testing app to confirm the environment when our own app which has a similar framework does not work.
We saw this issue in Edge a day or two ago and it was fixed by updating the core snap to beta. But as of this morning this no longer works ether.