Activity log for bug #581862

Date Who What changed Old value New value Message
2010-05-17 17:54:10 Dylan McCall bug added bug
2010-05-17 17:54:10 Dylan McCall attachment added Dependencies.txt http://launchpadlibrarian.net/48614290/Dependencies.txt
2010-07-29 21:36:33 Dylan McCall bug task added udev (Ubuntu)
2010-07-29 21:44:48 Dylan McCall description Binary package hint: tumiki-fighters Weird issue with this game. The ship appears to be stuck flying up and to the left. Thus, it is impossible to move down and the ship is always being pushed leftwards. This renders it unplayable ;) At first, it appears as thought the Down control simply does not work, regardless of which one I use. It may be specific to my system. I ran the Windows version of the game in Wine, and it works there. However, I did notice that controls became stuck in a similar fashion when another process rudely grabbed the keyboard and mouse, so the game is evidently quirky in how it handles input. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: tumiki-fighters 0.2.dfsg1-3build1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 17 10:16:13 2010 ProcEnviron: LANGUAGE=en_CA:en_GB:en LANG=en_CA.utf8 SHELL=/bin/zsh SourcePackage: tumiki-fighters I'm pretty well clueless as far as the input stack is concerned, so I hope I am aiming this report at the right place :) When I insert the Microsoft Nano Transceiver 1.0 (which comes with the MS Mobile Mouse 6000, for example) three input devices are created. Naturally, one of those corresponds to the mouse I am using, the other two are for other devices it could have been connected to. xinput lists these as two pointers and one keyboard. One of those pointers is a joystick (which udev sticks at /dev/js0). Even though I have no joystick associated with that transceiver (or indeed any joystick), games see that device and use it. The phantom joystick's position seems to be tilted upwards and to the left; in tumiki-fighter (where I noticed the problem), I am unable to control the game because I am stuck flying to the upper left corner of the screen. Here's some fun stuff… % xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Wacom Bamboo eraser id=13 [slave pointer (2)] ⎜ ↳ Wacom Bamboo cursor id=14 [slave pointer (2)] ⎜ ↳ Wacom Bamboo pad id=15 [slave pointer (2)] ⎜ ↳ Wacom Bamboo id=16 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=18 [slave pointer (2)] ⎜ ↳ Macintosh mouse button emulation id=19 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=11 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ USB 2.0 Camera id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=20 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=10 [slave keyboard (3)] % xinput query-state 10 1 class : KeyClass key[0]=up key[1]=up key[2]=up *Continues as so; all keys are up* % xinput query-state 12 3 classes : KeyClass key[0]=up key[1]=up key[2]=up *Snip* ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=960 valuator[1]=600 valuator[2]=0 valuator[3]=0 *All others (4 to 35) are 0* valuator[0] and valuator[1] look interesting ;) I installed the joystick package… % jstest --event /dev/input/js0 Driver version is 2.1.0. Joystick (Microsoft Microsoft® Nano Transceiver v1.0) has 37 axes (X, Y, Z, Rx, Ry, Rz, Throttle, Rudder, Wheel, Hat0X, Hat0Y, Hat1X, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null)) and 41 buttons (BtnThumbL, BtnThumbR, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), Btn0). Testing ... (interrupt to exit) Event: type 129, time 19221516, number 0, value 0 Event: type 129, time 19221516, number 1, value 0 Event: type 129, time 19221516, number 2, value 0 Event: type 129, time 19221516, number 3, value 0 Event: type 129, time 19221516, number 4, value 0 Event: type 129, time 19221516, number 5, value 0 Event: type 129, time 19221516, number 6, value 0 Event: type 129, time 19221516, number 7, value 0 Event: type 129, time 19221516, number 8, value 0 Event: type 129, time 19221516, number 9, value 0 Event: type 129, time 19221516, number 10, value 0 Event: type 129, time 19221516, number 11, value 0 Event: type 129, time 19221516, number 12, value 0 Event: type 129, time 19221516, number 13, value 0 Event: type 129, time 19221516, number 14, value 0 Event: type 129, time 19221516, number 15, value 0 Event: type 129, time 19221516, number 16, value 0 Event: type 129, time 19221516, number 17, value 0 Event: type 129, time 19221516, number 18, value 0 Event: type 129, time 19221516, number 19, value 0 Event: type 129, time 19221516, number 20, value 0 Event: type 129, time 19221516, number 21, value 0 Event: type 129, time 19221516, number 22, value 0 Event: type 129, time 19221516, number 23, value 0 Event: type 129, time 19221516, number 24, value 0 Event: type 129, time 19221516, number 25, value 0 Event: type 129, time 19221516, number 26, value 0 Event: type 129, time 19221516, number 27, value 0 Event: type 129, time 19221516, number 28, value 0 Event: type 129, time 19221516, number 29, value 0 Event: type 129, time 19221516, number 30, value 0 Event: type 129, time 19221516, number 31, value 0 Event: type 129, time 19221516, number 32, value 0 Event: type 129, time 19221516, number 33, value 0 Event: type 129, time 19221516, number 34, value 0 Event: type 129, time 19221516, number 35, value 0 Event: type 129, time 19221516, number 36, value 0 Event: type 129, time 19221516, number 37, value 0 Event: type 129, time 19221516, number 38, value 0 Event: type 129, time 19221516, number 39, value 0 Event: type 129, time 19221516, number 40, value 0 Event: type 130, time 19221516, number 0, value -32767 Event: type 130, time 19221516, number 1, value -32767 Event: type 130, time 19221516, number 2, value -32767 Event: type 130, time 19221516, number 3, value -32767 Event: type 130, time 19221516, number 4, value -32767 Event: type 130, time 19221516, number 5, value -32767 Event: type 130, time 19221516, number 6, value -32767 Event: type 130, time 19221516, number 7, value -32767 Event: type 130, time 19221516, number 8, value -32767 Event: type 130, time 19221516, number 9, value -32767 Event: type 130, time 19221516, number 10, value 0 Event: type 130, time 19221516, number 11, value 0 Event: type 130, time 19221516, number 12, value -32767 Event: type 130, time 19221516, number 13, value -32767 Event: type 130, time 19221516, number 14, value -32767 Event: type 130, time 19221516, number 15, value -32767 Event: type 130, time 19221516, number 16, value -32767 Event: type 130, time 19221516, number 17, value -32767 Event: type 130, time 19221516, number 18, value -32767 Event: type 130, time 19221516, number 19, value -32767 Event: type 130, time 19221516, number 20, value -32767 Event: type 130, time 19221516, number 21, value -32767 Event: type 130, time 19221516, number 22, value -32767 Event: type 130, time 19221516, number 23, value -32767 Event: type 130, time 19221516, number 24, value -32767 Event: type 130, time 19221516, number 25, value -32767 Event: type 130, time 19221516, number 26, value -32767 Event: type 130, time 19221516, number 27, value -32767 Event: type 130, time 19221516, number 28, value -32767 Event: type 130, time 19221516, number 29, value -32767 Event: type 130, time 19221516, number 30, value -32767 Event: type 130, time 19221516, number 31, value -32767 Event: type 130, time 19221516, number 32, value -32767 Event: type 130, time 19221516, number 33, value -32767 Event: type 130, time 19221516, number 34, value -32767 Event: type 130, time 19221516, number 35, value -32767 Event: type 130, time 19221516, number 36, value -32767 Later I tried running % jscal -c /dev/input/js0 It crashed, but indeed zeroed the imaginary joystick, so tumiki-fighter cooperated. If more data is needed, I am happy to provide it! Original bug report follows: Binary package hint: tumiki-fighters Weird issue with this game. The ship appears to be stuck flying up and to the left. Thus, it is impossible to move down and the ship is always being pushed leftwards. This renders it unplayable ;) At first, it appears as thought the Down control simply does not work, regardless of which one I use. It may be specific to my system. I ran the Windows version of the game in Wine, and it works there. However, I did notice that controls became stuck in a similar fashion when another process rudely grabbed the keyboard and mouse, so the game is evidently quirky in how it handles input. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: tumiki-fighters 0.2.dfsg1-3build1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 17 10:16:13 2010 ProcEnviron:  LANGUAGE=en_CA:en_GB:en  LANG=en_CA.utf8  SHELL=/bin/zsh SourcePackage: tumiki-fighters
2010-07-29 21:44:58 Dylan McCall tumiki-fighters (Ubuntu): status New Invalid
2010-07-29 21:49:48 Dylan McCall summary Keyboard controls are not functioning correctly Problematic joystick device with Microsoft Nano Transceiver
2010-08-26 13:32:54 Martin Pitt affects udev (Ubuntu) linux (Ubuntu)
2010-09-08 17:53:43 Jeremy Foshee tags apport-bug i386 lucid apport-bug i386 lucid needs-kernel-logs
2010-09-08 17:53:46 Jeremy Foshee tags apport-bug i386 lucid needs-kernel-logs apport-bug i386 lucid needs-kernel-logs needs-upstream-testing
2010-09-08 17:53:49 Jeremy Foshee tags apport-bug i386 lucid needs-kernel-logs needs-upstream-testing apport-bug i386 kj-triage lucid needs-kernel-logs needs-upstream-testing
2010-09-08 17:53:57 Jeremy Foshee linux (Ubuntu): status New Incomplete
2010-09-08 22:03:57 Dylan McCall linux (Ubuntu): status Incomplete New
2011-09-17 17:12:19 Brad Figg linux (Ubuntu): status New Incomplete
2011-09-18 01:55:49 Dylan McCall tags apport-bug i386 kj-triage lucid needs-kernel-logs needs-upstream-testing apport-bug apport-collected i386 kj-triage lucid needs-kernel-logs needs-upstream-testing oneiric staging
2011-09-18 01:55:52 Dylan McCall description I'm pretty well clueless as far as the input stack is concerned, so I hope I am aiming this report at the right place :) When I insert the Microsoft Nano Transceiver 1.0 (which comes with the MS Mobile Mouse 6000, for example) three input devices are created. Naturally, one of those corresponds to the mouse I am using, the other two are for other devices it could have been connected to. xinput lists these as two pointers and one keyboard. One of those pointers is a joystick (which udev sticks at /dev/js0). Even though I have no joystick associated with that transceiver (or indeed any joystick), games see that device and use it. The phantom joystick's position seems to be tilted upwards and to the left; in tumiki-fighter (where I noticed the problem), I am unable to control the game because I am stuck flying to the upper left corner of the screen. Here's some fun stuff… % xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Wacom Bamboo eraser id=13 [slave pointer (2)] ⎜ ↳ Wacom Bamboo cursor id=14 [slave pointer (2)] ⎜ ↳ Wacom Bamboo pad id=15 [slave pointer (2)] ⎜ ↳ Wacom Bamboo id=16 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=18 [slave pointer (2)] ⎜ ↳ Macintosh mouse button emulation id=19 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=11 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ USB 2.0 Camera id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=20 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=10 [slave keyboard (3)] % xinput query-state 10 1 class : KeyClass key[0]=up key[1]=up key[2]=up *Continues as so; all keys are up* % xinput query-state 12 3 classes : KeyClass key[0]=up key[1]=up key[2]=up *Snip* ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=960 valuator[1]=600 valuator[2]=0 valuator[3]=0 *All others (4 to 35) are 0* valuator[0] and valuator[1] look interesting ;) I installed the joystick package… % jstest --event /dev/input/js0 Driver version is 2.1.0. Joystick (Microsoft Microsoft® Nano Transceiver v1.0) has 37 axes (X, Y, Z, Rx, Ry, Rz, Throttle, Rudder, Wheel, Hat0X, Hat0Y, Hat1X, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null)) and 41 buttons (BtnThumbL, BtnThumbR, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), Btn0). Testing ... (interrupt to exit) Event: type 129, time 19221516, number 0, value 0 Event: type 129, time 19221516, number 1, value 0 Event: type 129, time 19221516, number 2, value 0 Event: type 129, time 19221516, number 3, value 0 Event: type 129, time 19221516, number 4, value 0 Event: type 129, time 19221516, number 5, value 0 Event: type 129, time 19221516, number 6, value 0 Event: type 129, time 19221516, number 7, value 0 Event: type 129, time 19221516, number 8, value 0 Event: type 129, time 19221516, number 9, value 0 Event: type 129, time 19221516, number 10, value 0 Event: type 129, time 19221516, number 11, value 0 Event: type 129, time 19221516, number 12, value 0 Event: type 129, time 19221516, number 13, value 0 Event: type 129, time 19221516, number 14, value 0 Event: type 129, time 19221516, number 15, value 0 Event: type 129, time 19221516, number 16, value 0 Event: type 129, time 19221516, number 17, value 0 Event: type 129, time 19221516, number 18, value 0 Event: type 129, time 19221516, number 19, value 0 Event: type 129, time 19221516, number 20, value 0 Event: type 129, time 19221516, number 21, value 0 Event: type 129, time 19221516, number 22, value 0 Event: type 129, time 19221516, number 23, value 0 Event: type 129, time 19221516, number 24, value 0 Event: type 129, time 19221516, number 25, value 0 Event: type 129, time 19221516, number 26, value 0 Event: type 129, time 19221516, number 27, value 0 Event: type 129, time 19221516, number 28, value 0 Event: type 129, time 19221516, number 29, value 0 Event: type 129, time 19221516, number 30, value 0 Event: type 129, time 19221516, number 31, value 0 Event: type 129, time 19221516, number 32, value 0 Event: type 129, time 19221516, number 33, value 0 Event: type 129, time 19221516, number 34, value 0 Event: type 129, time 19221516, number 35, value 0 Event: type 129, time 19221516, number 36, value 0 Event: type 129, time 19221516, number 37, value 0 Event: type 129, time 19221516, number 38, value 0 Event: type 129, time 19221516, number 39, value 0 Event: type 129, time 19221516, number 40, value 0 Event: type 130, time 19221516, number 0, value -32767 Event: type 130, time 19221516, number 1, value -32767 Event: type 130, time 19221516, number 2, value -32767 Event: type 130, time 19221516, number 3, value -32767 Event: type 130, time 19221516, number 4, value -32767 Event: type 130, time 19221516, number 5, value -32767 Event: type 130, time 19221516, number 6, value -32767 Event: type 130, time 19221516, number 7, value -32767 Event: type 130, time 19221516, number 8, value -32767 Event: type 130, time 19221516, number 9, value -32767 Event: type 130, time 19221516, number 10, value 0 Event: type 130, time 19221516, number 11, value 0 Event: type 130, time 19221516, number 12, value -32767 Event: type 130, time 19221516, number 13, value -32767 Event: type 130, time 19221516, number 14, value -32767 Event: type 130, time 19221516, number 15, value -32767 Event: type 130, time 19221516, number 16, value -32767 Event: type 130, time 19221516, number 17, value -32767 Event: type 130, time 19221516, number 18, value -32767 Event: type 130, time 19221516, number 19, value -32767 Event: type 130, time 19221516, number 20, value -32767 Event: type 130, time 19221516, number 21, value -32767 Event: type 130, time 19221516, number 22, value -32767 Event: type 130, time 19221516, number 23, value -32767 Event: type 130, time 19221516, number 24, value -32767 Event: type 130, time 19221516, number 25, value -32767 Event: type 130, time 19221516, number 26, value -32767 Event: type 130, time 19221516, number 27, value -32767 Event: type 130, time 19221516, number 28, value -32767 Event: type 130, time 19221516, number 29, value -32767 Event: type 130, time 19221516, number 30, value -32767 Event: type 130, time 19221516, number 31, value -32767 Event: type 130, time 19221516, number 32, value -32767 Event: type 130, time 19221516, number 33, value -32767 Event: type 130, time 19221516, number 34, value -32767 Event: type 130, time 19221516, number 35, value -32767 Event: type 130, time 19221516, number 36, value -32767 Later I tried running % jscal -c /dev/input/js0 It crashed, but indeed zeroed the imaginary joystick, so tumiki-fighter cooperated. If more data is needed, I am happy to provide it! Original bug report follows: Binary package hint: tumiki-fighters Weird issue with this game. The ship appears to be stuck flying up and to the left. Thus, it is impossible to move down and the ship is always being pushed leftwards. This renders it unplayable ;) At first, it appears as thought the Down control simply does not work, regardless of which one I use. It may be specific to my system. I ran the Windows version of the game in Wine, and it works there. However, I did notice that controls became stuck in a similar fashion when another process rudely grabbed the keyboard and mouse, so the game is evidently quirky in how it handles input. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: tumiki-fighters 0.2.dfsg1-3build1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 17 10:16:13 2010 ProcEnviron:  LANGUAGE=en_CA:en_GB:en  LANG=en_CA.utf8  SHELL=/bin/zsh SourcePackage: tumiki-fighters I'm pretty well clueless as far as the input stack is concerned, so I hope I am aiming this report at the right place :) When I insert the Microsoft Nano Transceiver 1.0 (which comes with the MS Mobile Mouse 6000, for example) three input devices are created. Naturally, one of those corresponds to the mouse I am using, the other two are for other devices it could have been connected to. xinput lists these as two pointers and one keyboard. One of those pointers is a joystick (which udev sticks at /dev/js0). Even though I have no joystick associated with that transceiver (or indeed any joystick), games see that device and use it. The phantom joystick's position seems to be tilted upwards and to the left; in tumiki-fighter (where I noticed the problem), I am unable to control the game because I am stuck flying to the upper left corner of the screen. Here's some fun stuff… % xinput list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Wacom Bamboo eraser id=13 [slave pointer (2)] ⎜ ↳ Wacom Bamboo cursor id=14 [slave pointer (2)] ⎜ ↳ Wacom Bamboo pad id=15 [slave pointer (2)] ⎜ ↳ Wacom Bamboo id=16 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=18 [slave pointer (2)] ⎜ ↳ Macintosh mouse button emulation id=19 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=11 [slave pointer (2)] ⎜ ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Sleep Button id=8 [slave keyboard (3)] ↳ USB 2.0 Camera id=9 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)] ↳ Asus Laptop extra buttons id=20 [slave keyboard (3)] ↳ Microsoft Microsoft® Nano Transceiver v1.0 id=10 [slave keyboard (3)] % xinput query-state 10 1 class : KeyClass key[0]=up key[1]=up key[2]=up *Continues as so; all keys are up* % xinput query-state 12 3 classes : KeyClass key[0]=up key[1]=up key[2]=up *Snip* ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=960 valuator[1]=600 valuator[2]=0 valuator[3]=0 *All others (4 to 35) are 0* valuator[0] and valuator[1] look interesting ;) I installed the joystick package… % jstest --event /dev/input/js0 Driver version is 2.1.0. Joystick (Microsoft Microsoft® Nano Transceiver v1.0) has 37 axes (X, Y, Z, Rx, Ry, Rz, Throttle, Rudder, Wheel, Hat0X, Hat0Y, Hat1X, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null)) and 41 buttons (BtnThumbL, BtnThumbR, (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), (null), Btn0). Testing ... (interrupt to exit) Event: type 129, time 19221516, number 0, value 0 Event: type 129, time 19221516, number 1, value 0 Event: type 129, time 19221516, number 2, value 0 Event: type 129, time 19221516, number 3, value 0 Event: type 129, time 19221516, number 4, value 0 Event: type 129, time 19221516, number 5, value 0 Event: type 129, time 19221516, number 6, value 0 Event: type 129, time 19221516, number 7, value 0 Event: type 129, time 19221516, number 8, value 0 Event: type 129, time 19221516, number 9, value 0 Event: type 129, time 19221516, number 10, value 0 Event: type 129, time 19221516, number 11, value 0 Event: type 129, time 19221516, number 12, value 0 Event: type 129, time 19221516, number 13, value 0 Event: type 129, time 19221516, number 14, value 0 Event: type 129, time 19221516, number 15, value 0 Event: type 129, time 19221516, number 16, value 0 Event: type 129, time 19221516, number 17, value 0 Event: type 129, time 19221516, number 18, value 0 Event: type 129, time 19221516, number 19, value 0 Event: type 129, time 19221516, number 20, value 0 Event: type 129, time 19221516, number 21, value 0 Event: type 129, time 19221516, number 22, value 0 Event: type 129, time 19221516, number 23, value 0 Event: type 129, time 19221516, number 24, value 0 Event: type 129, time 19221516, number 25, value 0 Event: type 129, time 19221516, number 26, value 0 Event: type 129, time 19221516, number 27, value 0 Event: type 129, time 19221516, number 28, value 0 Event: type 129, time 19221516, number 29, value 0 Event: type 129, time 19221516, number 30, value 0 Event: type 129, time 19221516, number 31, value 0 Event: type 129, time 19221516, number 32, value 0 Event: type 129, time 19221516, number 33, value 0 Event: type 129, time 19221516, number 34, value 0 Event: type 129, time 19221516, number 35, value 0 Event: type 129, time 19221516, number 36, value 0 Event: type 129, time 19221516, number 37, value 0 Event: type 129, time 19221516, number 38, value 0 Event: type 129, time 19221516, number 39, value 0 Event: type 129, time 19221516, number 40, value 0 Event: type 130, time 19221516, number 0, value -32767 Event: type 130, time 19221516, number 1, value -32767 Event: type 130, time 19221516, number 2, value -32767 Event: type 130, time 19221516, number 3, value -32767 Event: type 130, time 19221516, number 4, value -32767 Event: type 130, time 19221516, number 5, value -32767 Event: type 130, time 19221516, number 6, value -32767 Event: type 130, time 19221516, number 7, value -32767 Event: type 130, time 19221516, number 8, value -32767 Event: type 130, time 19221516, number 9, value -32767 Event: type 130, time 19221516, number 10, value 0 Event: type 130, time 19221516, number 11, value 0 Event: type 130, time 19221516, number 12, value -32767 Event: type 130, time 19221516, number 13, value -32767 Event: type 130, time 19221516, number 14, value -32767 Event: type 130, time 19221516, number 15, value -32767 Event: type 130, time 19221516, number 16, value -32767 Event: type 130, time 19221516, number 17, value -32767 Event: type 130, time 19221516, number 18, value -32767 Event: type 130, time 19221516, number 19, value -32767 Event: type 130, time 19221516, number 20, value -32767 Event: type 130, time 19221516, number 21, value -32767 Event: type 130, time 19221516, number 22, value -32767 Event: type 130, time 19221516, number 23, value -32767 Event: type 130, time 19221516, number 24, value -32767 Event: type 130, time 19221516, number 25, value -32767 Event: type 130, time 19221516, number 26, value -32767 Event: type 130, time 19221516, number 27, value -32767 Event: type 130, time 19221516, number 28, value -32767 Event: type 130, time 19221516, number 29, value -32767 Event: type 130, time 19221516, number 30, value -32767 Event: type 130, time 19221516, number 31, value -32767 Event: type 130, time 19221516, number 32, value -32767 Event: type 130, time 19221516, number 33, value -32767 Event: type 130, time 19221516, number 34, value -32767 Event: type 130, time 19221516, number 35, value -32767 Event: type 130, time 19221516, number 36, value -32767 Later I tried running % jscal -c /dev/input/js0 It crashed, but indeed zeroed the imaginary joystick, so tumiki-fighter cooperated. If more data is needed, I am happy to provide it! Original bug report follows: Binary package hint: tumiki-fighters Weird issue with this game. The ship appears to be stuck flying up and to the left. Thus, it is impossible to move down and the ship is always being pushed leftwards. This renders it unplayable ;) At first, it appears as thought the Down control simply does not work, regardless of which one I use. It may be specific to my system. I ran the Windows version of the game in Wine, and it works there. However, I did notice that controls became stuck in a similar fashion when another process rudely grabbed the keyboard and mouse, so the game is evidently quirky in how it handles input. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: tumiki-fighters 0.2.dfsg1-3build1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon May 17 10:16:13 2010 ProcEnviron:  LANGUAGE=en_CA:en_GB:en  LANG=en_CA.utf8  SHELL=/bin/zsh SourcePackage: tumiki-fighters --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: dylan 1855 F.... pulseaudio /dev/snd/controlC0: dylan 1855 F.... pulseaudio /dev/snd/controlC1: dylan 1855 F.... pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'DS'/'Asus Virtuoso 66 at 0xce00, irq 19' Mixer name : 'AV200' Components : 'WM8776 WM8766 AV200' Controls : 31 Simple ctrls : 25 Card1.Amixer.info: Card hw:1 'PCH'/'HDA Intel PCH at 0xfbff4000 irq 49' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,1458a022,00100004' Controls : 41 Simple ctrls : 23 Card2.Amixer.info: Card hw:2 'Generic'/'HD-Audio Generic at 0xfbdfc000 irq 50' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=3e136be3-9683-4cce-a9b6-ea7554ec5599 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110906) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3-B3 Package: linux (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-11-generic root=UUID=c3a1a202-a194-4446-9bdc-3ede97b07cfb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 RelatedPackageVersions: linux-restricted-modules-3.0.0-11-generic N/A linux-backports-modules-3.0.0-11-generic N/A linux-firmware 1.60 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no StagingDrivers: mei Tags: oneiric staging Uname: Linux 3.0.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 04/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: P67A-UD3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd.
2011-09-18 01:55:55 Dylan McCall attachment added AcpiTables.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419979/+files/AcpiTables.txt
2011-09-18 01:55:58 Dylan McCall attachment added AlsaDevices.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419980/+files/AlsaDevices.txt
2011-09-18 01:56:00 Dylan McCall attachment added AplayDevices.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419981/+files/AplayDevices.txt
2011-09-18 01:56:02 Dylan McCall attachment added ArecordDevices.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419982/+files/ArecordDevices.txt
2011-09-18 01:56:04 Dylan McCall attachment added BootDmesg.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419983/+files/BootDmesg.txt
2011-09-18 01:56:05 Dylan McCall attachment added Card0.Amixer.values.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419984/+files/Card0.Amixer.values.txt
2011-09-18 01:56:07 Dylan McCall attachment added Card1.Amixer.values.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419985/+files/Card1.Amixer.values.txt
2011-09-18 01:56:09 Dylan McCall attachment added Card1.Codecs.codec.2.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419986/+files/Card1.Codecs.codec.2.txt
2011-09-18 01:56:11 Dylan McCall attachment added Card2.Codecs.codec.0.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419987/+files/Card2.Codecs.codec.0.txt
2011-09-18 01:56:13 Dylan McCall attachment added CurrentDmesg.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419988/+files/CurrentDmesg.txt
2011-09-18 01:56:14 Dylan McCall attachment added IwConfig.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419989/+files/IwConfig.txt
2011-09-18 01:56:16 Dylan McCall attachment added Lspci.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419990/+files/Lspci.txt
2011-09-18 01:56:17 Dylan McCall attachment added Lsusb.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419991/+files/Lsusb.txt
2011-09-18 01:56:19 Dylan McCall attachment added PciMultimedia.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419992/+files/PciMultimedia.txt
2011-09-18 01:56:21 Dylan McCall attachment added ProcCpuinfo.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419993/+files/ProcCpuinfo.txt
2011-09-18 01:56:22 Dylan McCall attachment added ProcEnviron.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419994/+files/ProcEnviron.txt
2011-09-18 01:56:24 Dylan McCall attachment added ProcInterrupts.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419995/+files/ProcInterrupts.txt
2011-09-18 01:56:25 Dylan McCall attachment added ProcModules.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419996/+files/ProcModules.txt
2011-09-18 01:56:27 Dylan McCall attachment added PulseSinks.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419997/+files/PulseSinks.txt
2011-09-18 01:56:28 Dylan McCall attachment added PulseSources.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419998/+files/PulseSources.txt
2011-09-18 01:56:32 Dylan McCall attachment added UdevDb.txt https://bugs.launchpad.net/bugs/581862/+attachment/2419999/+files/UdevDb.txt
2011-09-18 01:56:35 Dylan McCall attachment added UdevLog.txt https://bugs.launchpad.net/bugs/581862/+attachment/2420000/+files/UdevLog.txt
2011-09-18 01:56:37 Dylan McCall attachment added WifiSyslog.txt https://bugs.launchpad.net/bugs/581862/+attachment/2420001/+files/WifiSyslog.txt
2011-09-18 01:57:18 Dylan McCall linux (Ubuntu): status Incomplete Confirmed
2011-09-24 07:31:07 Brad Figg linux (Ubuntu): status Confirmed Incomplete
2011-09-24 07:31:10 Brad Figg tags apport-bug apport-collected i386 kj-triage lucid needs-kernel-logs needs-upstream-testing oneiric staging apport-bug apport-collected i386 kernel-request-3.0.0-12.19 kj-triage lucid needs-kernel-logs needs-upstream-testing oneiric staging
2011-11-24 04:17:41 Launchpad Janitor linux (Ubuntu): status Incomplete Expired
2013-01-11 17:04:17 Timo Jyrinki linux (Ubuntu): status Expired Confirmed
2013-01-11 17:06:51 Timo Jyrinki bug task added linux
2013-01-11 17:10:23 Timo Jyrinki bug watch added http://bugzilla.kernel.org/show_bug.cgi?id=28912
2013-01-11 17:10:23 Timo Jyrinki linux: importance Undecided Unknown
2013-01-11 17:10:23 Timo Jyrinki linux: status New Unknown
2013-01-11 17:10:23 Timo Jyrinki linux: remote watch Linux Kernel Bug Tracker #28912
2013-01-11 17:13:30 Timo Jyrinki marked as duplicate 390959
2013-09-09 04:13:04 penalvch removed duplicate marker 390959
2013-09-09 04:14:41 penalvch summary Problematic joystick device with Microsoft Nano Transceiver 045e:0745 Problematic joystick device with Microsoft Nano Transceiver
2013-09-09 04:15:04 penalvch marked as duplicate 390959