I’ll let other people jump in for a snap-compliant solution, but as a quick workaround you should be able to temporarily disable the warnings by editing the apparmor profile in /var/lib/snapd/apparmor/profiles/snap.mir-kiosk.mir-kiosk and adding this line at the end (just before the last “}”):
The next time you start the mir-kiosk, you should not see these warnings anymore (with no other behavioural changes, since the accesses are still denied). I hope that this works in Ubuntu Core too.
IIRC the hardware-observe interface allows reading these nodes (at least in sysfs and proc, but /run likely only has links to either) … try adding it …
I think we want to eventually allow folks to specify rules which should be silenced some way, but it will take a bit of time to design and implement a solution for this. Can you file a LP bug about this? we may even already have such a bug, I don’t know
i do understand that, but today the only non-hackish way to do this on UC is to connect the interface that allows access … (and TBH i’d consider it rather a corner case that you get denials for something you do not want to actually access as well, most snaps actually want to access things they get denials for)