Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Arch Linux] Crashing upon initial use #143

Open
antaxiom opened this issue Feb 12, 2021 · 10 comments
Open

[Arch Linux] Crashing upon initial use #143

antaxiom opened this issue Feb 12, 2021 · 10 comments

Comments

@antaxiom
Copy link

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
@antaxiom
Copy link
Author

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.

@TauAkiou
Copy link
Contributor

Do you have an evdev rule set up to allow access? That might be your problem.

@antaxiom
Copy link
Author

antaxiom commented Feb 16, 2021 via email

@TauAkiou
Copy link
Contributor

TauAkiou commented Feb 16, 2021

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.

@antaxiom
Copy link
Author

antaxiom commented Feb 16, 2021 via email

@TauAkiou
Copy link
Contributor

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)/

@antaxiom
Copy link
Author

antaxiom commented Feb 16, 2021 via email

@TauAkiou
Copy link
Contributor

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.

@antaxiom
Copy link
Author

antaxiom commented Feb 16, 2021 via email

@antaxiom
Copy link
Author

antaxiom commented Apr 1, 2021

Hello, have you made any progress on this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants