Closed bosomt closed 4 years ago
and I experienced that I need ed to restart trezord process after i tried to send transaction or confirm address.
Process was running but http://127.0.0.1:21325/ was dead
windows 10 version stops responding after few minutes, attached logs from fresh installation 69MB
@tsusanka I just had an idea of updating bundled libusb to latest version (1.0.21->1.0.23). This is done in the libusb-update
branch. We might be hitting an issue that's been resolved in the libusb upstream. Let's try the bridge from this branch to see whether the issue magically resolves itself via the update.
Oh good idea! The branch fails however for mac and win build. I guess you have a better idea what went wrong so I won't debug it now. Let me know if I should.
I managed to fix the build failures for Mac+Win builds in the libusb-update
branch. Here is the latest output from Travis: https://travis-ci.org/github/trezor/trezord-go/builds/711423430
I have passed on the builds to QA.
QA no longer reports this!! 🎉🎉
@bosomt I think we can close?
@tsusanka happy to do that !
2.0.30 RC1 says LIBUSB_ERROR_ACCESS
Tested in :
latest Mint Linux: Chromium and Firefox latest Fedora Linux: Firefox
attaching log
log.gz