Re: [Bug 300143] Re: tablet devices show up as non-functional joysticks
> 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 already available (see http://bugzilla.kernel.org/show_bug.cgi?id=14049). i'm not sure why they haven't fixed this in the mainline kernel yet. janos -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300143] Re: tablet devices show up as non-functional joysticks
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300143] Re: tablet devices show up as non-functional joysticks
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 assumptions :-) -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300143] Re: tablet devices show up as non-functional joysticks
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 BTN_DIGI, BTN_TOUCH and all you can think off, then these blacklisting rules will fail basically :-) -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300143] Re: tablet devices show up as non-functional joysticks
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 track down, but i am on it at the moment. Until i found something specific here's the backtrace of my application so far: #0 0x7f48ea83a095 in raise () from /lib/libc.so.6 #1 0x7f48ea83baf0 in abort () from /lib/libc.so.6 #2 0x7f48ea8332df in __assert_fail () from /lib/libc.so.6 #3 0x7f48ea54c17d in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #4 0x7f48ea54d343 in _XSend () from /usr/lib/libX11.so.6 #5 0x7f48eb7c9625 in __glXFlushRenderBuffer () from /usr/lib/libGL.so.1 #6 0x7f48eb7cb35f in __glXSetupForCommand () from /usr/lib/libGL.so.1 #7 0x7f48eb7c7628 in glXSwapBuffers () from /usr/lib/libGL.so.1 #8 0x00418795 in draw_scene (arg=0x73e4bfe0) at /home/laubej/workspace/pallas/pallas/drawscene.cpp:306 #9 0x7f48eb30a3f7 in start_thread () from /lib/libpthread.so.0 #10 0x7f48ea8dfb2d in clone () from /lib/libc.so.6 #11 0x in ?? () Maybe someone else has an idea and can poke me into the right direction. It might be worth to notice that the rendering is done by MESA indirect glx, although i think that's not a problem with MESA at all. -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 track down, but i am on it at the moment. Until i found something specific here's the backtrace of my application so far: #0 0x7f48ea83a095 in raise () from /lib/libc.so.6 #1 0x7f48ea83baf0 in abort () from /lib/libc.so.6 #2 0x7f48ea8332df in __assert_fail () from /lib/libc.so.6 #3 0x7f48ea54c17d in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #4 0x7f48ea54d343 in _XSend () from /usr/lib/libX11.so.6 #5 0x7f48eb7c9625 in __glXFlushRenderBuffer () from /usr/lib/libGL.so.1 #6 0x7f48eb7cb35f in __glXSetupForCommand () from /usr/lib/libGL.so.1 #7 0x7f48eb7c7628 in glXSwapBuffers () from /usr/lib/libGL.so.1 #8 0x00418795 in draw_scene (arg=0x73e4bfe0) at /home/laubej/workspace/pallas/pallas/drawscene.cpp:306 #9 0x7f48eb30a3f7 in start_thread () from /lib/libpthread.so.0 #10 0x7f48ea8dfb2d in clone () from /lib/libc.so.6 #11 0x in ?? () Maybe someone else has an idea and can poke me into the right direction. It might be worth to notice that the rendering is done by MESA indirect glx, although i think that's not a problem with MESA at all. -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
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 track down, but i am on it at the moment. Until i found something specific here's the backtrace of my application so far: #0 0x7f48ea83a095 in raise () from /lib/libc.so.6 #1 0x7f48ea83baf0 in abort () from /lib/libc.so.6 #2 0x7f48ea8332df in __assert_fail () from /lib/libc.so.6 #3 0x7f48ea54c17d in _XGetXCBBuffer () from /usr/lib/libX11.so.6 #4 0x7f48ea54d343 in _XSend () from /usr/lib/libX11.so.6 #5 0x7f48eb7c9625 in __glXFlushRenderBuffer () from /usr/lib/libGL.so.1 #6 0x7f48eb7cb35f in __glXSetupForCommand () from /usr/lib/libGL.so.1 #7 0x7f48eb7c7628 in glXSwapBuffers () from /usr/lib/libGL.so.1 #8 0x00418795 in draw_scene (arg=0x73e4bfe0) at /home/laubej/workspace/pallas/pallas/drawscene.cpp:306 #9 0x7f48eb30a3f7 in start_thread () from /lib/libpthread.so.0 #10 0x7f48ea8dfb2d in clone () from /lib/libc.so.6 #11 0x in ?? () Maybe someone else has an idea and can poke me into the right direction. It might be worth to notice that the rendering is done by MESA indirect glx, although i think that's not a problem with MESA at all. -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
