Bug 141067

Summary: USB gamepad not working in user account but working in root account
Product: [openSUSE] SUSE LINUX 10.0 Reporter: j m <silvervein>
Component: OtherAssignee: Stefan Dirsch <sndirsch>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Minor    
Priority: P3 - Medium    
Version: Final   
Target Milestone: ---   
Hardware: i586   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description j m 2005-12-27 16:10:01 UTC 
I am running SUSE 10 EVALUATION final version on a 586i Dell Inspiron 7500 (intel coppermine 500Mhz).  I'm plugging in a Logitech WingMan Rumblepad into a 4 port generic USB hub that is plugged into my USB port.  When I try to play super tux with my user account the game does not react to the pad.  However, if I play super tux with the root account it works fine.

I used the usb monitor to confirm the pad is being recognized when I'm logged in as a user, no problem there, it identifies the pad with the same information as when I'm logged in as root.

I searched for a similar bug and found #112672.  Based on what I read there I checked /dev/input/ to see if there is a js* file when I'm in my user account and indeed I found it... so then I tried using the gamepad with the game pachi el marciano and found it works just like when I'm logged in as root.

Therefore, I presume the issue is with super tux, not SUSE.  I just wanted to let you know that there appears to be a dependency on whether a root or user account is logged in.

Any ideas on a workaround?  I've only been working with Linux/SUSE for 4 months so I would appreciate simple instructions.

Lastly, if you require follow-up on my part please note that I will be taking a 2 week vacation so there will be lag on my part.
Comment 1 Martin Lasarsch 2006-01-02 14:11:34 UTC 
not sure if we can fix this, nor if this is a real bug or a configuration issue. anyway, assigned to the maintainer. stefan, please close the bug if you think it's a config issue.
Comment 2 Stefan Dirsch 2006-01-02 14:40:54 UTC 
I'll try to reproduce this problem. Looks like a supertux bug when it works with Pachi.
Comment 3 Stefan Dirsch 2006-01-02 16:03:05 UTC 
Hmm ... I see the same problem for pachi and supertux here.

# strace -f -eopen pachi 2>&1|grep input
open("/dev/input/event0", O_RDONLY)     = -1 EACCES (Permission denied)
open("/dev/input/event1", O_RDONLY)     = -1 EACCES (Permission denied)
open("/dev/input/event2", O_RDONLY)     = -1 EACCES (Permission denied)

# strace -f -eopen supertux 2>&1|grep input
[pid  7532] open("/dev/input/event0", O_RDONLY) = -1 EACCES (Permission denied)
[pid  7532] open("/dev/input/event1", O_RDONLY) = -1 EACCES (Permission denied)
[pid  7532] open("/dev/input/event2", O_RDONLY) = -1 EACCES (Permission denied)

# ll /dev/input/event*
crw-r----- 1 root root 13, 64 2005-12-16 11:30 /dev/input/event0
crw-r----- 1 root root 13, 65 2005-12-16 11:30 /dev/input/event1
crw-r----- 1 root root 13, 66 2005-12-16 11:30 /dev/input/event2


And currently I don't have an USB joystick/gamepad for testing available. :-(
Comment 4 Stefan Dirsch 2006-09-01 15:45:48 UTC 
Could you check this again with openSUSE 10.2 >= Alpha3?
Comment 5 Stefan Dirsch 2006-10-27 15:48:53 UTC 
openSUSE 10.2 Beta1 has just been released.
Comment 6 Stefan Dirsch 2006-11-30 00:20:26 UTC 
To prevent this bugreport remaining open for the time being I close
this one now as fixed - assuming it *is* fixed. Don't hesitate to
reopen it again if you still can reproduce it with openSUSE >= 10.2.
The final release of openSUSE 10.2 is scheduled for 2006-12-07.