JInput on Ubuntu

Engines, Libraries and Tools JInput
#1

hi,

I get this output if I use JInput (latest version) on linux:


Loading: net.java.games.input.LinuxEnvironmentPlugin
Failed to open device (/dev/input/event8): Failed to open device /dev/input/event8 (13)

Failed to open device (/dev/input/event7): Failed to open device /dev/input/event7 (13)

Failed to open device (/dev/input/event3): Failed to open device /dev/input/event3 (13)

Failed to open device (/dev/input/event1): Failed to open device /dev/input/event1 (13)

Failed to open device (/dev/input/event2): Failed to open device /dev/input/event2 (13)

Failed to open device (/dev/input/event5): Failed to open device /dev/input/event5 (13)

Failed to open device (/dev/input/event4): Failed to open device /dev/input/event4 (13)

Failed to open device (/dev/input/event6): Failed to open device /dev/input/event6 (13)

Failed to open device (/dev/input/event0): Failed to open device /dev/input/event0 (13)

also the array returned by ControllerEnvironment.getDefaultEnvironment().getControllers() is empty.

no problems on windows (same system)

#2

Marvin from Xith3d once pointed out, that jinput needed root-priviledges or changed access-rights on the input devices it wants to use in the past. This was the major blocker for using jinput as default input manager. Maybe the situation is the same now.

#3

For non rumbling devices, jinput just needs read access. If you want to rumble, it needs write too. We use the standard /dev/input/event device nodes, if you can’t read from them, jinput can’t read from the controller.

/dev/input/js devices on nearly all flavours are read enabled by default, /dev/input/event are not, and that’s what causes the issue.

HTH

Endolf

#4

Thank you both for the answer. The read privileges caused that problem.