System reboot if using two lightgun
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
I configured my RetroArch station with UDEV input driver so i can use two usb mice as lightgun. Everything works fine, I have two crosshairs working separate and i can play. The problem arises after a few minutes (1 or 2) during game; my Ubuntu 20.04 system reboots and no kernel crash dump is logged (I activated crashdump for this scope). The crash happens ONLY if i move both mice together...if i leave one mouse locked (no pointer events generated) the system seems to be stable and working.
hope it helps.
Expected behavior
Two mice working as lightgun
Actual behavior
My system crashes as an hardware reboot.
Steps to reproduce the bug
- Open RetroArch
- Load Flycast Core / Mame2003-Plus core (I tried these ones)
- Load content (I used HOTD2/The maze of the king for Naomi and Area51 for Mame2003-Plus)
- Start play
- Enter quick menu
- configure controller 1 mouse index as my first mouse
- configure controller 2 mouse index as my second mouse
- Back to game
- Play; the crosshairs works indipendently one another for both core and i can play a little
- the system crashes abruptly.
Bisect Results
I've updated on last RetroArch and Flycast/Mame2003-Plus revision 'cause i've seen there was a bug for lightgun indexing.
Version/Commit
- Retroarch 1.10.0 - e9e85f3
- GCC 9.4.0 64bit
Environment information
- OS: XUbuntu 20.04
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reboot with the UDEV input driver, two USB mice, and the Flycast and Mame2003-Plus cores on Ubuntu 20.04. Use the quick menu's controller mouse-index configuration as the entry point; done means both independent crosshairs remain usable without an abrupt system reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, ubuntu
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100