Socket activation for Wayland interface


#1

I was hoping to use Socket Activation to avoid startup races between mir-kiosk and client snaps. However, we need to create the wayland socket in a shared location (it is defined as being in $XDG_RUNTIME_DIR).

After consideration we now make the socket /run/user/0/wayland-0 and both clients and servers access this through the wayland interface.

However, with snapd, socket activation only works for “$SNAP_DATA and $SNAP_COMMON prefixes” and that excludes /run/user/0/wayland-0.

Any suggestions?


Update: let’s keep discussion on https://forum.snapcraft.io/t/socket-activation-for-well-known-locations/


Chromium-mir-kiosk on-screen keyboard