[Bug 35954] Dead Space (Steam) crashes on startup (some Microsoft keyboard and mouse devices are incorrectly recognised as joystick, reporting nonsense caps/data)

wine-bugs at winehq.org wine-bugs at winehq.org
Thu Apr 24 07:09:55 CDT 2014


http://bugs.winehq.org/show_bug.cgi?id=35954

Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
           See Also|                            |https://bugzilla.kernel.org
                   |                            |/show_bug.cgi?id=37982
            Summary|Dead Space (Steam) crashes  |Dead Space (Steam) crashes
                   |on startup                  |on startup (some Microsoft
                   |                            |keyboard and mouse devices
                   |                            |are incorrectly recognised
                   |                            |as joystick, reporting
                   |                            |nonsense caps/data)
     Ever confirmed|0                           |1

--- Comment #14 from Anastasius Focht <focht at gmx.net> ---
Hello Rob,

--- quote ---
Huh, I don't even have a joystick. I just removed the device node for now (no
idea why it's being populated), and the game works!!
--- quote ---

you probably have this one: 'Microsoft Wired Keyboard 600'

There is a kernel bug reported here:
https://bugzilla.kernel.org/show_bug.cgi?id=37982 ("Microsoft Wired Keyboard
600 create a spurious joystick device.")

These devices report nonsense data when being incorrectly recognized as joy
devices (hid).

Maybe Wine should blacklist all input devices with vendor id == 0x045e
(Microsoft) to be safe ... j/k :)

Well, at least those that are obviously invalid: 

--- snip ---
0020:trace:dinput:JoystickWGenericImpl_GetCapabilities 0x923f4e4->(0x3c9f1b4)
0020:trace:dinput:_dump_DIDEVCAPS dwSize: 44
0020:trace:dinput:_dump_DIDEVCAPS dwFlags: 00000001
0020:trace:dinput:_dump_DIDEVCAPS dwDevType: 00000214 UNKNOWN
0020:trace:dinput:_dump_DIDEVCAPS dwAxes: 8
0020:trace:dinput:_dump_DIDEVCAPS dwButtons: 57
0020:trace:dinput:_dump_DIDEVCAPS dwPOVs: 1
0020:trace:dinput:_dump_DIDEVCAPS dwFFSamplePeriod: 0
0020:trace:dinput:_dump_DIDEVCAPS dwFFMinTimeResolution: 0
0020:trace:dinput:_dump_DIDEVCAPS dwFirmwareRevision: 0
0020:trace:dinput:_dump_DIDEVCAPS dwHardwareRevision: 0
0020:trace:dinput:_dump_DIDEVCAPS dwFFDriverVersion: 0 
--- snip ---

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987622

https://bbs.archlinux.org/viewtopic.php?id=142469

http://ryort.wordpress.com/2011/12/04/udev-and-the-microsoft-digital-media-keyboard-3000-wha/

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/390959

The root cause is of course 'upstream'.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list