As for your enroute flight navigation snap, the same thing applies.
You need plugs like desktop
, desktop-legacy
, wayland
and x11
for your graphical application. If you don’t need that very specific Qt version you’re building (and only need amd64
builds) (https://github.com/Akaflieg-Freiburg/enrouteSnap/blob/55257fe7252ccda2431764d23c2d7112dda001e6/snap/snapcraft.yaml#L19), I’d again suggest the use of the kde-neon
extension to get rid of all that headache inducing Qt stuff.
In general, you can use methods described in Debugging snaps to get an idea what plugs/permissions are lacking (. snappy-debug
will outright point you to possible solutions.
I tested enroute
like so: snap install --devmode enroute-flight-navigation
. This allowed me to launch the app, which means the problem is a problem of missing permissions/plugs. snappy-debug
told me
Log: apparmor="DENIED" operation="connect" profile="snap.enroute-flight-navigation.enroute" pid=71429 comm="enroute" family="unix" sock_type="stream" protocol=0 requested_mask="send receive connect" denied_mask="send connect" addr=none peer_addr="@/tmp/.X11-unix/X1" peer="unconfined"
You can see that it wants to connect to the X-server, but fails to do so because it lacks permission to do so.