Wayland sockets


As part of kiosk type setup, we use mir-kiosk, and an “app” snap with a plug connected to the the wayland interface.

We have been setting up a symlink to the socket file /run/user/0/wayland-0 in the snap location /run/user/0/snap.some-app-snap/wayland-0

However, I’ve recently noticed that something is overwriting that symlink with an real socket file. Is that something snapd is now doing automagically if the wayland interface plug is connected to a snap ?

I can’t see anything in the app snap that would be doing it. So I’m puzzled if it’s not snapd, and would welcome any other ideas.


Nothing has changed:

$ snap run --shell mir-kiosk-kodi 
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.

$ ls -lh $XDG_RUNTIME_DIR/
total 0
lrwxrwxrwx 1 alan alan 24 Jun 17 10:05 wayland-0 -> /run/user/1000/wayland-0
lrwxrwxrwx 1 alan alan 29 Jun 17 10:05 wayland-0.lock -> /run/user/1000/wayland-0.lock

Does it only happen in your snap?

Hmmm, curious.

ok - perhaps I’ve missed something. I will do some more digging, it must be in the snap somewhere.

Thanks for confirming it’s not something outside the snap @alan_g :+1:

Cheers, Just