search

LedgerHQ / ledger-live-desktop

⛔️ DEPRECATED - Ledger Live (Desktop)
https://www.ledger.com/live
MIT License
953 stars 301 forks source link

Ledger device: Internal error, please report (0x6f01) #1386

Closed dmflahive closed 3 years ago

dmflahive commented 6 years ago

Ledger device: Internal error, please report (0x6f01)

I get this error every time I try to send currency. On both MacOS and Windows.

meriadec commented 6 years ago

Can you specify which app is used?

dmflahive commented 6 years ago

Both BTC and LTC give this error.

How is this invalid? My currency is currently locked in the wallet and I can't get it out.

meriadec commented 6 years ago

The error 0x6f01 indicates a technical problem while communicating with the device (see btchip-doc). You can start testing with another usb port, another usb cable, another computer and see if it's working.

If still not working, can you try sending your funds with the legacy Chrome app?

dmflahive commented 6 years ago

Thank you for that information. I have already tried a different cable and USB port and it still doesn't work, but I can accept that it may not be the software. I'm using a 2018 MacBook Pro with a usb-c to usb-a adapter I get the feeling there may be something lost in the conversion there.

I see that the legacy app is working now. When I submitted the ticket the legacy app would force me to download Ledger Live without the option to use the app.

dmflahive commented 6 years ago

So the legacy app is working fine, I just sent funds using it. Ledger Live is still giving the following error: Ledger device: Internal error, please report (0x6f01). Seems like it must be a software issue if the legacy app works but Live doesn't using the same wallet, same USB port, etc...

If you are able to reproduce the issue and would like for me to test on my end just let me know.

meriadec commented 6 years ago

Thanks for the details. As you said, if legacy app is working but not Live, it's probably a software problem (there is also one other possibility: Chrome app is using chrome-hid for USB connection, while Live is node-hid).

I reopen this

samacumen commented 6 years ago

I confirm. LTC giving problem. Tried sending LTC several times still get:

Something went wrong!
Ledger device: Internal error, please report (0x6f01)

Using Ubuntu 16.04 LTS and Ledger Live ApplImage run with or without sudo, the same error.

Someone kindly fix this asap.

northbound1 commented 6 years ago

Same here sending LTC Win 10.

ledger live error

meriadec commented 6 years ago

We may want to try to add delay between each APDU call (parametrable with environment variable). Seen with firmware team, it can happen when device is sollicitated too much.

samacumen commented 6 years ago

The only workaround (for now) I found for this is to use the standard Chrome App for Bitcoin and open Litecoin on your ledger with it. Use Legacy Litecoin address to send. All should work until LedgerLive is fixed.

rocknet commented 6 years ago

What is the difference between 6f00 and 6f01? This issue is very similar to the one Zen users are experiencing, but the code for us is 6f00: https://github.com/LedgerHQ/ledger-live-desktop/issues/1239

cryptofiend commented 6 years ago

I'm having exactly the same issue trying to send LTC from my nano S using Ledger Live. I'm using a 2018 MacBook Pro with a USB-C to USB-A dongle. Tried all four USB-C ports, same result. Was finally able to send LTC using the legacy Chrome app. Please don't kill the legacy Chrome app until this is fixed!

ncodedbpm commented 6 years ago

Yes I also have had a ticket into support for a while now on this issue for LTC. Please do not get rid of the legacy app.

molotovah commented 6 years ago

Same problem with Ledger Live transfering BTC

gre commented 6 years ago

We may want to try to add delay between each APDU call (parametrable with environment variable). Seen with firmware team, it can happen when device is sollicitated too much.

@meriadec i forgot to address this in the incoming release, but we'll try to do something in next sprint. I think it's an interesting idea but i'm not sure it would actually help, we might also review our transport code. One scenario I know that can create problem for sure is if you open 2 apps that use the ledger at same time, there going to be problems.

Ideally we need to be in the same setup some person have the bug and systematically reproduce it.

meriadec commented 6 years ago

Also, interesting hint raised by @amougel is being on the manager page while having add/send/receive modal opened. The background page continuously ping the device (I thought we paused that!) and that sounds bad.

gre commented 6 years ago

we should be protected by withDevice tho.

The problem you raise is to me a UX problem. should not be able to Send/Receive from manager.

gre commented 6 years ago

what about having some "cooldown" between each withDevice so we have some time to let the device catch up if needed?

amougel commented 6 years ago

@gre some device calls are blocking, just waiting is not enough if user action is required. I think the manager should be disabled if a modal is present, why would we want to update a screen that is masked by a modal and that you can't interact with.

gre commented 6 years ago

I agree with the "manager spinning behind" problem. it's just not easy to implement to change this. Also, what i'm saying is I think it's likely a non problem for tech (it's a UX problem). we have a lock system, called withDevice, that would prevent any concurrent call with the device. if something is blocking on the device, it is still not redeemed from the promise, any other attempt to do something with the device would just wait. the fact concurrent job happen would just slow down the global things. it's like CPU multi-tasking. now if you tell me there is a bug that potentially two concurrent APDU exchanges break the device, we have a wider problem than this manager thing

meriadec commented 6 years ago

What can be easily done is to make the Manager a modal (big modal), so one does not simply open two modals at the same time

gre commented 6 years ago

what about we disable Send and Receive button if you are on Manager. or we force the navigation to go Portfolio if you click it

meriadec commented 6 years ago

Yes, even smaller to implement

cmbconcretefire commented 6 years ago

Hey guys, I REALLY don't mean to be a ball buster, but I need fast help. I am getting the same exact error trying to send LTC. (Oddly enough, I DID NOT have trouble sending LTC just last week on ledger live??) Anyway.....that is no concern to me. All I care about is ..... I need to get my LTC OUT ....so can someone take me by the hand and step by step show me what I need to install now? (Or Uninstall and then install) and where to get everything I need to do so? (Links please)

I don't need actual step by step. I understand the process. Just need a link or something to get me fixed up. I'm currently using ledger live. LTC Legacy account. HELP. Thanks.

cmbconcretefire commented 6 years ago

update, I figured out how to do via the old chrome app (Ledger Wallet Bitcoin) and the TX sent......HOWEVER......I am now sitting at 22 minutes and only have 4 confirmations.......I understand this is legacy....but that is not acceptable. Meanwhile....price continues to drop. LEDGER LIVE obviously has a problem, it's been known for at least 22 days now.....and no fix......also unacceptable.

gre commented 6 years ago

This issue is hard for us to tackle because no one from our internal teams was able to reproduce it. If the issue was easy to fix, it would have been from the start but we are aware there is a bug based on all the feedback we got on this problem.

As it was mentioned here, one potential idea of what the problem can be is too much exchange done with the device, therefore i've sent a PR attempting to fix the bug following this idea.

https://github.com/LedgerHQ/ledger-live-desktop/pull/1549

As no one from our develop team was able to reproduce the problem, we encourage our community to help us testing this, investigating on the problem and experimenting solutions.

Thanks!

RudyBouwman commented 6 years ago

I am getting this error when sending DigiBytes. Have send a ticket to Support and added a log file.

sameersbn commented 5 years ago

I faced this issue while sending a transaction in the cashaddr format (BCH). I had to convert the address to the legacy format for it to work.

alighazi commented 5 years ago

I still have this issue when sending BCH

shak3nbak3 commented 4 years ago

I got this error on Particl QT when I updated Ledger to 1.6. At first it was the 0x6f01 error, and then progressed to AddStandardInputs failed: [default wallet] PrepareTransaction for device failed: Dongle error: 4af7 Unknown.

The GUI says: AddStandardInputs failed: No device found

I swapped ports and cables with no luck. The legacy chrome app doesn't work with NANO S 1.6