Device 3-16 RX aborted due to error or disconnect

[libimobiledevice]

Device 3-16 RX aborted due to error or disconnect

[blshkv]

It might be something to do my usb controller. I've tried to pass-through usb port to virtual machine and got the follow warning:
Warning: speed mismatch trying to attach usb device "iPad" (high speed) to bus "usb-bus.0", port "1" (full speed)

Bus 002 Device 019: ID 05ac:12ab Apple, Inc.
lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
        |__ Port 1: Dev 12, If 0, Class=Wireless, Driver=rndis_host, 480M
        |__ Port 1: Dev 12, If 1, Class=CDC Data, Driver=rndis_host, 480M
        |__ Port 2: Dev 19, If 0, Class=Imaging, Driver=, 480M
        |__ Port 2: Dev 19, If 1, Class=Vendor Specific Class, Driver=, 480M
        |__ Port 2: Dev 19, If 2, Class=Vendor Specific Class, Driver=, 480M

I'm unable to change the speed using the command below:
echo -2 > /sys/bus/usb/devices/usb2/../companion
https://www.kernel.org/doc/Documentation/ABI/testing/sysfs-bus-pci-drivers-ehci_hcd

[FunkyM]

The error is not on your end. The device simply disconnects and the trust dialog is not handled properly with your versions of the library.
You need to be running libimobiledevice >= 1.1.6 and upcoming usbmuxd 1.0.9 (or git HEAD).

[blshkv]

You might want to re-open the ticket because problem is not fully fixed for me. I've upgraded to the latest versions and HEAD of usbmuxd COMMIT="8ba560fdd177f107c5a0cf667d4e4ab3b0c59f4a".

I can see idevice_id now, however ideviceinfo does not work:

Mar 25 23:28:23 [usbmuxd] [1] config_get_device_record: failed to read '/var/lib/lockdown/597f61afb660f2e8a8d24ee85657a19e7ef11ccd.plist': No such file or directory_

bash$ ls /var/lib/lockdown
SystemConfiguration.plist

However, iproxy works fine. Thanks!

[FunkyM]

Well, ideviceinfo should work. The error above indicates that you have not paired with the device as usbmuxd is unable to read a corresponding pair record from /var/lib/lockdown/. The message itself is not an error and expected if you have not paired with the device yet. Ensure usbmuxd has the permissions for file operations in /var/lib/lockdown/. Furthermore, running "ideviceinfo -d" should reveal what is going wrong and report an error that you can post here.