hi @kottens - just for extra clarity, the additional system-files interface files you’re looking for auto-connection are apart of shell-config-files which are:
hi @cav
hm… this is a bit surprising, apparmor would clearly flag the violation for me without this line. isn’t this template bit mainly for non-core systems? this snap is for use on a core system.
This is the PR making the interface usable on Core systems:
It is not an implicit slot on core because the services the application would talk to are running as part of a desktop session snap, as is being done here.
@jamesh@kottens just to be sure, is auto-connection desired for screen-inhibit-control? If I’m right, In that case all snaps will auto-connect to plasma-desktop-session:screen-inhibit-control
Then, +1 from me for granting plasma-desktop-session slot auto-connection on the screen-inhibit-control.
It seems that the store dashboard does not allow reviewers to grant declarations for screen-inhibit-control, as it still says “This is a rule for a system only interface. No other snap can have such slots.”. I’ll ping the store team to get this fixed