TF2 SIGSEGV if you have Xbox 360 Wireless Receiver plugged in

[76561198076225808]

What the title says.

I had the Xbox 360 Wireless Receiver plugged into my PC and this causes TF2 on linux to segfault on start up.

Presumably this has something to do with the /dev/input/event* interfaces that the Receiver has and which TF2 is checking at startup.

Unplugging it gets me a bit closer towards TF2 on linux... :-)

[Sno]

Happens to me with my wireless microsoft keyboard and mouse.

[Mikkel]

Happens to me also. Possibly due to the vendor name?

[] usb 3-3: >Manufacturer: \xffffffc2\xffffffa9\xffffffa9Microsoft

[FiggyG]

I'm also affected.

[76561198076225808]

I thought "fixed a common joystick crash" in the last update referred to this.

Evidently not.

Easy enough to workaround thankfully.

[flibitijibibo]

Out of curiosity, what do you get when you put the receiver through this?

http://www.flibitijibibo.com/files/VesselJoystickDetector.c

I recently dealt with a segfault in Eversion and a bug in Vessel that had to do with one of Microsoft's wireless keyboard/mouse transmitters... in SDL, it was acting like a controller with something ridiculous like 30 axes and 50 buttons. You may get something similar with the 360 wireless receiver... if so, post the device info from that C program here.

As far as I know, if there's no way to disable joystick input, you have to just ignore the device if it has that specific name. Looks sucky in code, but it does the job.

[76561198076225808]

Początkowo opublikowane przez flibitijibibo:

Out of curiosity, what do you get when you put the receiver through this?

Gamepad: Xbox 360 Wireless Receiver
Number of axes: 6
Number of hats: 0
Number of buttons: 15

Awaiting new joystick input...

Axis #0, Config value: 0

[Benjamin]

If you use the "xboxdrv" driver instead of the built-in xpad module, it doesn't crash. It's a much better driver, with proper LED support and lots of customization options. The quick and dirty way to get running is to install xboxdrv (from Ubuntu repos or PPA), and put the following at the end of your /etc/rc.local file (before exit 0):

rmmod xpad
xboxdrv --silent --mimic-xpad

[76561198076225808]

Początkowo opublikowane przez Benjamin:

If you use the "xboxdrv" driver instead of the built-in xpad module, it doesn't crash. It's a much better driver, with proper LED support and lots of customization options. The quick and dirty way to get running is to install xboxdrv (from Ubuntu repos or PPA), and put the following at the end of your /etc/rc.local file (before exit 0):

rmmod xpad
xboxdrv --silent --mimic-xpad

Thanks for the info.

[Benjamin]

No problem. Xboxdrv is a much better driver all around. I might write up a newbie-thread about how to install it in Ubuntu if there is interest, since that's what most people new to Linux are using. People not on Ubuntu tend to not need any guidance on these things.

[76561198076225808]

Początkowo opublikowane przez Benjamin:

No problem. Xboxdrv is a much better driver all around. I might write up a newbie-thread about how to install it in Ubuntu if there is interest, since that's what most people new to Linux are using. People not on Ubuntu tend to not need any guidance on these things.

Installing it is trivial, knowing it exists was really the only thing (although I note post #4 suggests it doesn't stop the crash)

But, in some ways it's moot, the game shouldn't crash with either driver.

[ZeXx86 [Linux]]

Same problem with classic joystick

[Benjamin]

Strange, stops the crash for me...