This really seems like a libX11 problem, not a specific java one. I am
currently developing an opengl application an stumbled on that problem
while testing my program on ubuntu hardy amd64. In my case the problem
occurs when calling glXSwapBuffers(), but not continuesly. therefore
it's hard to trac
This really seems like a libX11 problem, not a specific java one. I am
currently developing an opengl application an stumbled on that problem
while testing my program on ubuntu hardy amd64. In my case the problem
occurs when calling glXSwapBuffers(), but not continuesly. therefore
it's hard to trac
This really seems like a libX11 problem, not a specific java one. I am
currently developing an opengl application an stumbled on that problem
while testing my program on ubuntu hardy amd64. In my case the problem
occurs when calling glXSwapBuffers(), but not continuesly. therefore
it's hard to trac
> Hi, I am using an X-52 with X-Plane 9 under Karmic - this used to work
> fine, (Last used it in November or so) but the X-52 is no longer
> detected. (Kernel 2.6.31-17-generic) Is there any experiment I can do
> that will help debug/resolve this?
hi. no, basically not, since there is a fix alre
the fix causes a regression in 2.6.28-15. the saitek x52 and x52pro
joysticks get blacklisted now too, i.e. the joystick device
/dev/input/js* won't be created.
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because
thanks for fixing. how are chances that the fix will make it into 2.6.32
mainline? :-)
--
tablet devices show up as non-functional joysticks
https://bugs.launchpad.net/bugs/300143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
i'm not subscribed to that list, but browsing the archive i found
following statement in the mentioned thread:
> I find it doubtful that the device actually has 39 buttons...
can someone make it clear that the X52 actually has 39 buttons. it seems
that they're working again on the base of assumpt
i don't know much about the input subsystem of the kernel, but wouldn't
it be better to just blacklist devices according to their vendor and
product id if applicable, and not according to features they may or may
not have? someday there might be a grafic tablet with integrated mini
joystick, using
