search

mame82 / UnifyingVulnsDisclosureRepo

Formerly private repository for discussion, knowledge- and code-sharing around new Unifying vulns, as announced on Twitter
154 stars 27 forks source link

handle_events: error: libusb: interrupted [code -10] #9

Open grymoire opened 1 year ago

grymoire commented 1 year ago

I'm getting many errors: Is this normal? 2023/02/17 13:33:09 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:09 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:10 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:10 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:10 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:10 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:11 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:12 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:12 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:13 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:14 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:14 handle_events: error: libusb: interrupted [code -10] 2023/02/17 13:33:15 handle_events: error: libusb: interrupted [code -10]

smannchen commented 1 year ago

No. Try a different usb cable, reinstall dependencies, reboot.

also-here commented 1 year ago

They are fairly normal messages from libusb that should probably be DEBUG instead of ERROR. You can simply hide them by adding 2&>/dev/null to the end of the command you're running (e.g../mjackit pairsniff 2&>/dev/null), or some other file instead of /dev/null if you want to save them and other possible error messages.