jinput; polling mouse events does not work properly

[bienator]

Hi,

I can successfully poll mousebuttons and keyboard but the x,y  and mousewheel value stays at 0. Are there known issues on Ubuntu 8.10? It worked for me on 7.10 (and on windows of course).

/dev/input/* is readable for everyone.

[endolf]

Hi

I've just updated my laptop to 8.10 and see the same thing, it's a new bug, I'll do some digging.

Cheers

Endolf

[endolf]

I've had a look this evening at this. Seems that event trying to cat the /dev/input/event* devices doesn't work, so JInput has no change. Going to a real terminal rather than a virtual one in X seems to kick everything in to life, so I'm guessing it's an X issue. I've done a bit of hunting but I've not found an answer yet. It's definitely the OS rather than JInput though.

Endolf

Games published by our own members! Check 'em out!

[bienator]

thank you for looking into it endolf,

maybe you could file a bug report against ubuntu? I don't think I have enough background knowledge to provide useful information

[paulalexandrow]

Hi,

having encountered the same problem, i did some research myself and might be able to shed some more light on this topic: the problem seems to be related to the introduction of input-hotplug for X11 in Intrepid (see [1]). Further, roaming through a couple of Ubuntu forums, I found that there were people facing more severe side effects than just /dev/input/* having no output, such as no working keyboard at all, etc.  There are some suggested workarounds for their problems too, one of which worked for me: put

1	Option   "AutoAddDevices" "false"

into the "ServerFlags" section of your xorg.conf and restart the X server. Voila: cat /dev/input/* reflects mouse movements again and JInput correctly reads those values as well.

Honestly, being a total nitwit in terms of X11, I don't even know what this setting really effects. It's just something I found out and wanted to share with anybody who might be able to address the problem properly and could benefit from this information (and anybody who, just like me, can continue developing for the time being).

Needless to say, that this can only be a short-term, dev-only workaround for me, as it can't be expected of any normal user or customer to change some system-config (leaving aside any necessary chmods on /dev/input/*). Therefore I would very much appretiate any solution that works with standard-Intrepid and standard-JInput - whatever needs to be changed for that. Yeah, needless to say...

[1] http://www.ubuntu.com/getubuntu/releasenotes/810#X.Org%20Input%20Devices

PS: Having just started with JInput today and being new to JGO as well let me please say hello and thank you for the wonderful Jinput API!

[endolf]

Yup, thats the same thread I saw. I'm not sure what the side effects are though. I think the new X doesn't have a comprehensive config file by default, it guesses most stuff each time. IIRC the mouse and keyboard is now supported using Xs evdev driver, and I don't know what effect the flag has on those. Any volunteers to shaft their X config??

Endolf