Bug 6110 - Laptop's mouse is seen as a joystick
Summary: Laptop's mouse is seen as a joystick
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-05-27 01:46 CEST by Larry Bolan
Modified: 2013-11-23 16:15 CET (History)
1 user (show)

See Also:
Source RPM: ?
CVE:
Status comment:


Attachments

Description Larry Bolan 2012-05-27 01:46:52 CEST
Description of problem:

When one goes to setup thier joystick, rather than popping up the "press button" screen and waiting for user input, it defaluts almost instantly to "axis 0 -". Even when the device is disbled, it still does this on the device's settings page.

During gameplay, the joystick works fine if using the default settings (axis 0 doesn't hang in either direction). The issue only occurs

I am not sure if this is realted, but I am using a modified xbox controller via the xpad module. 

In cauldron this was workign fine, even after I changed the repos when 2 became stable. This only seems to happen on fresh installs.



Version-Release number of selected component (if applicable):


How reproducible:

Easily

Steps to Reproduce:
1. go to the settings menu of STK
2. try to edit the profile for your joystick by selection a function to re-assign.
Manuel Hiebel 2012-05-28 12:50:43 CEST

Assignee: bugsquad => mageia
Source RPM: (none) => supertuxkart

Comment 1 Larry Bolan 2012-06-06 10:59:28 CEST
After some experimentation, I found a possible cause of the problem.

First, unlike my upgraded install on another computer, STK recognized the receiver to my Microsoft wireless mobile mouse 6000 as an imput device.

I also discovered that despite only having my gamepad plugged in, there were two joysticks in /dev/input, js0 and js1.

I then used jstest to discover that js1 represented the gamepad, while js0 represented something else.

After running "rm /dev/imput/js0", my mouse no longer showed up as an input device in STK and I was able to properly setup my gamepad.

Therefore, whatever is causing my microsoft wireless receiver to register as a joystick is likely the cause of this bug.
Comment 2 Larry Bolan 2012-06-06 11:02:42 CEST
Edit to above: the command I ran was "rm /dev/input/js0".
Comment 3 Damien Lallement 2012-06-18 18:38:06 CEST
Assigning back to bugsquad as it's not a SuperTuxKart issue.
N.B: are you on a laptop? Sometime, mouse is seen as a joystick.

Assignee: mageia => bugsquad
Source RPM: supertuxkart => (none)

Comment 4 Larry Bolan 2012-06-18 19:23:44 CEST
Yup, its a laptop.
Comment 5 Samuel Verschelde 2013-08-29 11:38:02 CEST
On my laptop, it's the accelerometer that is seen as a joystick, so it's even worse :)

I don't know what the solution to this could be. I wonder how other distributions manage this kind of issue.

CC: (none) => stormi
Summary: SuperTuxKart defaults to "axis 0 -" for all joystick settings => Laptop's mouse is seen as a joystick

Samuel Verschelde 2013-08-29 11:38:50 CEST

Source RPM: (none) => ?

Comment 6 Samuel Verschelde 2013-08-29 11:46:43 CEST
Is the problem still present in Mageia 3?

Keywords: (none) => NEEDINFO

Comment 7 Manuel Hiebel 2013-10-22 12:19:09 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 8 Manuel Hiebel 2013-11-23 16:15:47 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.