blobsaver crashes when reading APNonce on Linux

[Grelo4ka]

Describe the bug
After clicking "Read from device" in the APNonce field, my iPhone enters the recovery mode successfully. However, right after that, blobsaver crashes (I attach the logs below).

Screenshots
N/A

Desktop:

• OS Version: Arch Linux
• iOS Device: iPhone 12 Pro

Checklist (place an x between the brackets to mark as completed):

• I have made sure I am on the latest version of blobsaver
• I have checked other open issues to see if my problem has already been reported
• I have tried common troubleshooting tactics such as restarting my computer and reinstalling blobsaver

Log(s)

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f3dac0eaac5, pid=66544, tid=66614
#
# JRE version: OpenJDK Runtime Environment Zulu18.30+11-CA (18.0.1+10) (build 18.0.1+10)
# Java VM: OpenJDK 64-Bit Server VM Zulu18.30+11-CA (18.0.1+10, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C  [libusb-1.0.so.0+0xdac5]  libusb_get_device_descriptor+0x25
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/grelo4ka/core.66544)
#
# An error report file with more information is saved as:
# /home/grelo4ka/hs_err_pid66544.log
#
# If you would like to submit a bug report, please visit:
#   http://www.azul.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you would like this to remain open, please comment, otherwise this issue will be closed in 5 days.'

[Grelo4ka]

Still not working

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you would like this to remain open, please comment, otherwise this issue will be closed in 5 days.'

[Grelo4ka]

The issue is still present

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you would like this to remain open, please comment, otherwise this issue will be closed in 5 days.'

[0xf0xx0]

I have the same issue on my iPhone 12. My logfile is attached below.

hs_err_pid7433.log

[Tuerpe]

me too here. IPhone 13 Pro Max
hs_err_pid10312.log

[airsquared]

Does the fix in #459 work?

[Grelo4ka]

Does the fix in #459 work?

Nope, running blobsaver with sudo does not solve this issue

[airsquared]

If it doesn't work won't sudo either, it's likely not a bug in blobsaver but a problem with your installation or computer.

The log shows the program crashes in libusb, so I'd check your version of libusb and your usb setup first.

[0xf0xx0]

The log shows the program crashes in libusb, so I'd check your version of libusb and your usb setup first.

i wasn't able to get it to work in macOS either (running Catalina), although ill have to re-run it to get the logfile. will edit with results.

E: tried latest release (3.3.0), it works on macOS now (cool!) but still fails on linux (not cool!)
my libusb version is 1.0.26.

[airsquared]

Try building/installing libusb from master. If that doesn't work try building and installing libplist, libimobiledevice, and libirecovery from master as well.

[0xf0xx0]

Building libusb, libplist, libimobiledevice, and libirecovery from master worked.

libusb: gba698478
libplist: ge2a030a
libimobiledevice: g3a10a31
libirecovery: ge017429