Regression: GFCE Ultra no longer recognizes Logitech Gamepad cross arrows

Bug #357245 reported by komputes
4
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fceu (Ubuntu)
Invalid
Undecided
Unassigned
gfceu (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When setting up the input device in GFCE Ultra, the button recognition dialog no longer recognizes Gamepad cross arrows for up, down, right, and left. It only recognizes the two "Analog Control" buttons which are not as precise.

Hardware: 046d:c216 Logitech, Inc. Dual Action Gamepad
Kernel module: usbhid

fceu has remained the same version (0.98.12-3) from hardy to karmic. GFCE Ultra no longer recognizes the cross arrows in version 0.6.1-0ubuntu1 (Jaunty) yet works perfectly on 0.6.0-0ubuntu2 (Intrepid).

This bug may be caused by any of the following:
gfceu -> fceu -> usbcore (kernel module) -> usbhid (kernel module)

linux-image-`uname -r`: /lib/modules/`uname -r`/kernel/drivers/hid/usbhid/usbhid.ko

As fceu has not changed versions and gfceu is just a front-end. I believe the culprit that does not allow the arrows to work in the later driver is the usbhid driver. Bug also reported against linux project.

Please include instructions to give a more detailed report (if necessary).

komputes (komputes)
description: updated
Revision history for this message
Sean Fitzpatrick (sean-fitzpatrick) wrote :

I'm having similar problems with this gamepad since upgrading to 9.10 Beta, in my case with Supertuxkart (much to the annoyance of my girlfriend...)

Revision history for this message
komputes (komputes) wrote :

I can confirm this bug still exists in Ubuntu 9.10 (Kernel 2.6.31). Any chance of getting this input device driver recognizing the keys for Lucid (LTS).

Revision history for this message
komputes (komputes) wrote :

Sean and I have been in discussion and he has let me know that the "Mode" button on this gamepad switches from the joystick (when off) to the cross arrows (when on). I am now marking this as invalid, as I had misunderstood the purpose of the mode button.

Changed in fceu (Ubuntu):
status: New → Incomplete
status: Incomplete → Invalid
Changed in gfceu (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.