Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#38960 - [pcsx2] OnePAD crashes program when gamepad is plugged in
Attached to Project:
Community Packages
Opened by Tim Van den Langenbergh (tmtvl) - Tuesday, 18 February 2014, 21:54 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 21 February 2014, 08:42 GMT
Opened by Tim Van den Langenbergh (tmtvl) - Tuesday, 18 February 2014, 21:54 GMT
Last edited by Maxime Gauduin (Alucryd) - Friday, 21 February 2014, 08:42 GMT
|
DetailsDescription:
When setup for OnePAD is clicked while gamepad is plugged in, the process is killed without any message in the terminal. Error message according to gdb: Program received signal SIGSEGV, Segmentation fault. 0xf7255216 in __strlen_sse2_bsf () from /usr/lib32/libc.so.6 Additional info: * package version(s) * config and/or log files etc. I am using the latest versions straight from the Arch package database. Steps to reproduce: Run PCSX2 with a gamepad plugged in. Choose the default OnePAD plugin for the gamepad (if not yet) and click Configure... I have reported this on the official forums, and they told me to ask the maintainer for a debug package that contains debug symbol (I have used abs and added the '!strip' and 'debug' options to the PKGBUILD and installed that). I'm new to this, so sorry if I've done something wrong. |
This task depends upon
Closed by Maxime Gauduin (Alucryd)
Friday, 21 February 2014, 08:42 GMT
Reason for closing: Fixed
Additional comments about closing: pcsx2 1.2.2-2
Friday, 21 February 2014, 08:42 GMT
Reason for closing: Fixed
Additional comments about closing: pcsx2 1.2.2-2
gdbbacktrace.txt
One thing you can also try is build pcsx2 without SDL2, remove 'sdl2' from the depends array, and set SDL2_API to 'FALSE' in the cmake line. If SDL2 is the culprit, I'll ship pcsx2 built against SDL1.
Just so I know, what gamepad are you trying to use? I can try with a 360 controller and an older Saitek gamepad later today.
Also, sorry for the slow response, my ISP was unhappy with my usage.