Snap access to /dev/uinput
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
I'm trying to create snap package for application that is "driver" for my joystick (remaps buttons, creates virtual joystick):
https:/
As I didn't find useful documentation (nor examples) for snap hardware access, so I'd like to ask here:
Can snap package have access to /dev/uinput?
I've already seen, but doesn't seem useful:
http://
http://
I've seen something that might be usefull - Cgroups, but the info is too general:
https:/
Can you answer question is such application can be build in snap (and be useful)?
Can snap have access to /dev/uinput?
If yes where to find information about it?
summary: |
- Snap access to /dev/uinput? Possible? + Snap access to /dev/uinput? |
description: | updated |
Changed in snappy: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
affects: | snappy → snapd |
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.