Community Packages

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!
Tasklist

FS#76716 - [sdl2][pcsx2] resetting repeat rate for keyboard

Attached to Project: Community Packages
Opened by Lenny (Lenny03) - Friday, 02 December 2022, 05:20 GMT
Last edited by Toolybird (Toolybird) - Monday, 19 December 2022, 20:51 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: As the title says, PCSX2 from arch repos will reset the keyboard repeat rate.


Additional info: Seems to happen with both the packaged version, and AUR compiled version, may be a QT issue as stated in the github bug report, though it doesnt happen in the appimages provided on the PCSX2 website
* package version(s) pcsx2 1.7.3546-1
* config and/or log files etc. N/A Happens regardless of config being changed.
* link to upstream bug report, if any https://github.com/PCSX2/pcsx2/issues/7514

Steps to reproduce: Open the program.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 19 December 2022, 20:51 GMT
Reason for closing:  Upstream
Comment by Toolybird (Toolybird) - Friday, 02 December 2022, 05:55 GMT
Cannot repro using the steps provided. What DE/WM environment? xorg or wayland? Does the changed repeat rate reflect in settings i.e `xset q' output or equivalent?
Comment by Lenny (Lenny03) - Friday, 02 December 2022, 06:10 GMT
Using i3wm, xorg of course. After I open pcsx2 it changes from
"auto repeat delay: 200 repeat rate: 62"
to
"auto repeat delay: 660 repeat rate: 25"
Comment by Lenny (Lenny03) - Friday, 02 December 2022, 06:32 GMT
Seems like when I disable this option in the controllers section it fixes it, but at the same time it also disables my being able to use the controller I have, also when I check dmesg with that option selected, and start pcsx2 it logs
"[15530.398922] usbhid 5-2:1.2: Razer Device disconnected
[15538.496825] usbhid 5-2:1.0: Razer Device disconnected
[15540.504684] input: Razer Razer BlackWidow as /devices/pci0000:00/0000:00:08.1/0000:0f:00.3/usb5/5-2/5-2:1.0/0003:1532:0241.0083/input/input156
[15540.556848] razerkbd 0003:1532:0241.0083: input,hidraw0: USB HID v1.11 Keyboard [Razer Razer BlackWidow] on usb-0000:0f:00.3-2/input0"
   20221202012819.png (57.8 KiB)
Comment by Toolybird (Toolybird) - Friday, 02 December 2022, 06:47 GMT
Ok, so possibly SDL related. What happens if you temporarily roll back to sdl2-2.24.2-1 from your pkg cache?
Comment by Lenny (Lenny03) - Friday, 02 December 2022, 06:51 GMT
OK, after seeing disabling sdl input source fixes the keyboard issue, I downgraded sdl2 to version 2.24.2-1 and it seems to fix the issue, so this may be an sdl2 regression?
Comment by Toolybird (Toolybird) - Friday, 02 December 2022, 07:10 GMT
> so this may be an sdl2 regression?

Yes, it seems like it. Just had a quick search of their issues [1] and couldn't spot anything obvious. Probably best if you report it there. Please let us know what you find out.

[1] https://github.com/libsdl-org/SDL/issues
Comment by Toolybird (Toolybird) - Monday, 19 December 2022, 20:51 GMT
https://github.com/libsdl-org/SDL/issues/6733

Fix should be in next release.

Loading...