-
Notifications
You must be signed in to change notification settings - Fork 76
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
Doesn't exit (libusb problem?) #129
Comments
I haven't seen that error before. What version of libusb are you using? |
1.0.19 |
What about pyusb? |
Probably this issue I think: https://github.com/walac/pyusb/issues/66. |
pyusb-1.0.0b2. OK; thanks. I'll check into walac/pyusb#66. As with the reporter @ walac/pyusb#66, I'm also on python 3.4. So looks probable. |
If I understood it correctly, the patch fixing walac/pyusb#66 had been merged into walac/pyusb master, but I'm having the same issue even though having built and installed the latter. |
Hm yes, that is weird. if you run
That is the correct version? If it is finding the correct pyusb installation and this still occurs, I'm afraid I have no idea what is wrong. |
Trying to see if I might get help from project walac/pyusb. |
@walac asked for a test script to reproduce the issue (over at pyusb#66). I haven't dabbled in Python before, so instead of trying to scrape your code for tidbits which might make up a test script reproducing this issue, I'll ask you first. Would it be possible for you @Tigge to make some minimal script which should(n't) lead to the error message above @ comment 61684472? |
I think you are using the version built from master you should have version |
I had none installed through package manager (portage). When trying to fix this, I installed something that looked related through pip. Removed that now.
But, alas,
|
Seems antfs-cli doesn't exit properly, even though it's done.
I get this:
Emphasis being on the last line. Stalls there. I get that this might be libusb's issue, not antfs-cli, but do you have any idea what might be done to fix it?
The text was updated successfully, but these errors were encountered: