JoyShockMapper
JoyShockMapper copied to clipboard
JibbSmart
[Arch Linux] Crashing upon initial use
Hello, I've gotten into more control customization on Linux and I've been unhappy with steam's solutions for games that are non steam. I decided to try this out as I liked the innovative ideas. However, upon launching the program it suddenly stops on me, this is the output I am given.
Error
Failed to create virtual device: No such device
Failed to create virtual device: No such device
Welcome to JoyShockMapper version v2.2.0!
Initialising Bluetooth connection...
Not a USB response...
Attempting USB connection
Getting MAC...
Doing handshake...
Switching baudrate...
Doing handshake...
Only talk HID...
Enabling vibration...
Enabling IMU data...
Getting calibration data...
Could not initialise Pro Controller! Will try again later.
Initialising Bluetooth connection...
Not a USB response...
Attempting USB connection
Getting MAC...
Doing handshake...
Switching baudrate...
Doing handshake...
Only talk HID...
Enabling vibration...
Enabling IMU data...
Getting calibration data...
Body: 0x323232; Buttons: 0xffffff; Left Grip: 0xffffff; Right Grip: 0xffffff;
Successfully initialized Pro Controller!
2 devices connected
After this my shell tells me the program has stopped, these are the different errors for each shell if one ends up being more useful than the other.
fish:
fish: “JoyShockMapper” terminated by signal SIGSEGV (Address boundary error)
bash:
Segmentation fault (core dumped)
zsh:
[1] 719798 segmentation fault (core dumped) JoyShockMapper
Expected Behaviour
The program opens up as normal and I can utilize it for games
Additional notes:
- I'm running the AUR package
- I'm using the latest kernel
- I'm running a Nintendo Switch Pro controller
- Whether I have controls connected or not it still crashes
I've tried compiling the program myself and I've noticed that when the pro controller is connected it fails, maybe it has to do with the 5.10 kernel Nintendo HID Driver. I'm still unsure, if anyone could give me some ideas I could do more research.
Do you have an evdev rule set up to allow access? That might be your problem.
I'm not sure what evdev is, I looked it up and it has to do with gamepads on linux, but beyond that I don't know what I need to do to "allow access".
On Tue, Feb 16, 2021 at 8:58 AM TauAkiou [email protected] wrote:
Do you have an evdev rule set up to allow access? That might be your problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JibbSmart/JoyShockMapper/issues/143#issuecomment-779820172, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRW3ARN564W7FDLPPBG3NDS7JTYLANCNFSM4XQRCX7Q .
Sorry, I got a bit confused there. It's udev.
JoyShockMapper comes with a udev rules file that needs to be installed in /etc/udev/rules.d.
If that's not the case, I'll look into it - I get a segfault on first connection but it never seems to happen again after I restart JoyShockMapper.
As for the udev rules file, does the aur package install that for me? Also when I build it manually where's that udev file?
I just wanted to note a few things: Segfault always happens, but what happens before varies depending on what controllers are connected, ect.
On Tue, Feb 16, 2021 at 9:25 AM TauAkiou [email protected] wrote:
Sorry, I got a bit confused there. It's udev.
JoyShockMapper comes with a udev rules file that needs to be installed in /etc/udev/rules.d.
If that's not the case, I'll look into it - I get a segfault on first connection but it never seems to happen again after I restart JoyShockMapper.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JibbSmart/JoyShockMapper/issues/143#issuecomment-779835113, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRW3ARNQLMZMJMSPPSWWCDS7JW5PANCNFSM4XQRCX7Q .
If the udev file was included with the AUR, it should have been copied into /etc/udev/rules.d or /usr/lib/udev/rules.d (https://wiki.archlinux.org/index.php/Udev)
If you build it manually, the udev file should be included with the source code (dist/linux/50-joyshockmapper.rules)/
I just checked and I already have the udev file in the
/usr/lib/udev/rules.d. I'm still getting the same segfault as before. I'm
not quite sure what's going on.
On Tue, Feb 16, 2021 at 9:44 AM TauAkiou [email protected] wrote:
If the udev file was included with the AUR, it should have been copied into /etc/udev/rules.d or /usr/lib/udev/rules.d ( https://wiki.archlinux.org/index.php/Udev)
If you build it manually, the udev file should be included with the source code (dist/linux/50-joyshockmapper.rules)/
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JibbSmart/JoyShockMapper/issues/143#issuecomment-779845714, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRW3AXPN63L2YMIA3PAULTS7JZEZANCNFSM4XQRCX7Q .
I can't seem to recreate this problem - that's why I asked about udev, but I'm lost. I may need to set up an Arch machine to try and diagnose it myself.
I think trying out an arch machine would probably be ideal, I'm not sure what info I could give you.
On Tue, Feb 16, 2021 at 10:57 AM TauAkiou [email protected] wrote:
I can't seem to recreate this problem - that's why I asked about udev, but I'm lost. I may need to set up an Arch machine to try and diagnose it myself.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/JibbSmart/JoyShockMapper/issues/143#issuecomment-779891143, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJRW3AU67XGJ4WYRK6O25O3S7KBW7ANCNFSM4XQRCX7Q .