Comment 17 for bug 1257591

Revision history for this message
Stephen Tiedemann (stephen-tiedemann) wrote :

This is not a Python version issue but related to libus/pyusb. The root cause seems to be that libusb fails to claim the interface for the USB device and returns some error code that the _check() method in pyusb wants to raise up the stack. Then conversion of the error code to an error string fails because the libusb dynamic library doesn't have the libusb_strerror function.

Without knowing what pyUSB wants to say about the problem with claim_interface, it's speculative to say what might have caused the issue first place. However, a common cause would be that some another process has already claimed it or there are insufficient access permissions.