Thank you for filing a bug. /dev/uinput is not currently included in pluggable interfaces and a new interface would need to be added for it. While that is not the case, you are free to use devmode for your snap.
Note to snappy developers, /dev/uinput gives very privileged access to input events. AFAIK the kernel doesn't (currently) provide a way to mediate these events based on device (ie, giving snap access to udev events for only a joystick) and /dev/uinput is not needed by typical applications (it is used by display servers like mir).
I suspect if this were to be implemented as an interface, we would likely call it 'input-control', and it would not auto-connect. Then in the future fine-grained mediation for uinput could be explored.
Thank you for filing a bug. /dev/uinput is not currently included in pluggable interfaces and a new interface would need to be added for it. While that is not the case, you are free to use devmode for your snap.
Note to snappy developers, /dev/uinput gives very privileged access to input events. AFAIK the kernel doesn't (currently) provide a way to mediate these events based on device (ie, giving snap access to udev events for only a joystick) and /dev/uinput is not needed by typical applications (it is used by display servers like mir).
I suspect if this were to be implemented as an interface, we would likely call it 'input-control', and it would not auto-connect. Then in the future fine-grained mediation for uinput could be explored.