Ledger-live-desktop: Can't add BTC/BCH/DASH (something wen't wrong during synchronization)

[infestdead]

Ledger Live Version and Operating System

• Ledger Live 1.0.0
• Platform: Linix (Fedora 28)

Expected behavior

I expected to be able to add my BTC/BCH/DASH accounts.

Actual behavior

Adding BTC/BCH/DASH doesn't work. I get the following error:

Also please note - ETH works.

Steps to reproduce the behavior

1. Download official latest ledger live AppImage
2. Run, follow instructions.
3. Try and add BTC/BCH or DASH.

[KhalilBellakrid]

@infestdead thank you for reporting the bug, is it possible to check in the log file where the error occurs and paste it here? (make sure there is no personal info in the logs you send here)

[infestdead]

Yes, sure - do you mean the ~/.config/Ledger Live/logs/application-2018-07-09.log file? If so - it's 1.8MB and in JSON format or similar, and seem very painstaking to check for personal info. Is there a way to upload it privately or at least let me know what information might I need to delete from the log.

[KhalilBellakrid]

Yes I can understand, you can check for all suspicious errors that happen during synchronization:

• Network errors,
• Internal processor errors

Or anything suspicious in libcoreSyncAccount step of concerned accounts

Thanks !

[thetestspecimen]

I have the exact same problem. This also applies to LTC, and I suppose any coin that is based on Bitcoin.

Using: Fedora 28 and version "ledger-live-desktop-1.0.1-linux-x86_64.AppImage"

Here is the error section of the log (I have replaced the wallet instance with [removed]. I think I have not left any sensitive data below, but please let me know if I have:

{"type":"libcore","level":"info","message":"🛠 Info: 2018-07-09T23:08:08Z+03:00 I: Building wallet instance '**[removed]**__bitcoin' for bitcoin with parameters: \n","pname":"internal","timestamp":"2018-07-09T20:08:08.877Z"} {"level":"warn","message":"Internal process ended with code null","pname":"main","timestamp":"2018-07-09T20:08:09.381Z"} {"type":"cmd.ERROR","data":{"message":"Internal process error (null)","name":"InternalError"},"level":"warn","message":"✖ CMD listenDevices error","pname":"renderer","timestamp":"2018-07-09T20:08:09.382Z"} {"level":"info","message":"booting internal process...","pname":"main","timestamp":"2018-07-09T20:08:09.419Z"} {"message":"listenDevices error","name":"InternalError","level":"warn","pname":"renderer","timestamp":"2018-07-09T20:08:09.382Z"} {"type":"action","action":{"type":"RESET_DEVICES"},"level":"info","message":"⚛️ RESET_DEVICES","pname":"renderer","timestamp":"2018-07-09T20:08:09.382Z"} {"level":"info","message":"info","pname":"renderer","timestamp":"2018-07-09T20:08:09.419Z"} {"type":"cmd.ERROR","data":{"message":"Internal process error (null)","name":"InternalError"},"level":"warn","message":"✖ CMD libcoreScanAccounts error","pname":"renderer","timestamp":"2018-07-09T20:08:09.419Z"} {"level":"info","message":"Internal process is up!","pname":"internal","timestamp":"2018-07-09T20:08:09.836Z"} {"level":"info","message":"info","pname":"internal","timestamp":"2018-07-09T20:08:09.849Z"} {"type":"cmd.NEXT","data":{"type":"add","descriptor":"/dev/hidraw0","device":{"vendorId":11415,"productId":1,"path":"/dev/hidraw0","serialNumber":"0001","manufacturer":"Ledger","product":"Nano S","release":512,"interface":0,"usagePage":14897,"usage":11825}},"level":"info","message":"● CMD listenDevices","pname":"internal","timestamp":"2018-07-09T20:08:09.856Z"} {"type":"cmd.NEXT","data":{"descriptor":"/dev/hidraw0","device":{"interface":0,"manufacturer":"Ledger","path":"/dev/hidraw0","product":"Nano S","productId":1,"release":512,"serialNumber":"0001","usage":11825,"usagePage":14897,"vendorId":11415},"type":"add"},"level":"info","message":"● CMD listenDevices","pname":"renderer","timestamp":"2018-07-09T20:08:09.857Z"} {"type":"action","action":{"type":"ADD_DEVICE","payload":{"interface":0,"manufacturer":"Ledger","path":"/dev/hidraw0","product":"Nano S","productId":1,"release":512,"serialNumber":"0001","usage":11825,"usagePage":14897,"vendorId":11415}},"level":"info","message":"⚛️ ADD_DEVICE","pname":"renderer","timestamp":"2018-07-09T20:08:09.857Z"} {"type":"action","action":{"type":"MODAL_CLOSE","payload":{"name":"MODAL_ADD_ACCOUNTS"}},"level":"info","message":"⚛️ MODAL_CLOSE","pname":"renderer","timestamp":"2018-07-09T20:08:15.653Z"} {"type":"anaytics-track","properties":{},"level":"info","message":"△ track CloseModalAddAccounts","pname":"renderer","timestamp":"2018-07-09T20:08:16.149Z"}

[infestdead]

Here's my log, tried updating the bitcoin etc apps to latest 1.2.6 - problem persists.

ledger-live.log

[bocekm]

The same here too. Let me know if I can help with investigating or testing.
Ledger Nano (1.4.2 firmware), Ledger Live 1.0.1 on Fedora 28.

Removing all apps from Nano and installing back e.g. just Bitcoin app does not help. The standard output in terminal does not show any error, just the UI.

I don't think it's Bitcoin-based coins problem only. I tried adding Monero (dev) and I'm getting the same error.

What I think might be related is that in the Manager window, I don't have the green check mark for the installed apps, those I can see in the promo video of Ledger Live:

Even after installing an app, there's the Install button again. So it seems that the app is struggling with getting the info about apps installed on the Nano.

[gre]

@bocekm you have spotted a difference between expectation and reality :)

I hope we can make the expectation dream come true in a near future tho 🚀

[checco]

Same here. When I'm trying to add BTC account I have a lot of this errors when Ledger Live is telling me to

Open the Bitcoin app on your device

{"type":"cmd.ERROR","data":{"name":"TransportStatusError","message":"Ledger device: Security not satisfied (dongle locked or have invalid access rights) (0x6982)","stack":"Error\n    at TransportStatusError (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/@ledgerhq/hw-transport/lib/Transport.js:152:16)\n    at TransportNodeHid._callee$ (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/@ledgerhq/hw-transport/lib/Transport.js:205:23)\n    at tryCatch (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/regenerator-runtime/runtime.js:62:40)\n    at Generator.invoke [as _invoke] (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/regenerator-runtime/runtime.js:296:22)\n    at Generator.prototype.(anonymous function) [as next] (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/regenerator-runtime/runtime.js:114:21)\n    at step (/tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)\n    at /tmp/.mount_ledgerGaTbJy/app/resources/app.asar/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13\n    at <anonymous>","statusCode":27010,"statusText":"SECURITY_STATUS_NOT_SATISFIED"},"level":"warn","message":"✖ CMD getAddress error","pname":"internal","timestamp":"2018-07-10T23:00:15.125Z"}

And then after I have opened the BTC app I have on the log the following messages:

{"type":"libcore","level":"info","message":"🛠  Info: 2018-07-11T01:05:20Z+02:00 I: Building wallet instance '[...]' for bitcoin with parameters: \n","pname":"internal","timestamp":"2018-07-10T23:05:20.891Z"}
{"level":"warn","message":"Internal process ended with code null","pname":"main","timestamp":"2018-07-10T23:05:21.815Z"}
{"type":"cmd.ERROR","data":{"message":"Internal process error (null)","name":"InternalError"},"level":"warn","message":"✖ CMD listenDevices error","pname":"renderer","timestamp":"2018-07-10T23:05:21.816Z"}
{"level":"info","message":"booting internal process...","pname":"main","timestamp":"2018-07-10T23:05:21.866Z"}
{"message":"listenDevices error","name":"InternalError","level":"warn","pname":"renderer","timestamp":"2018-07-10T23:05:21.816Z"}
{"type":"action","action":{"type":"RESET_DEVICES"},"level":"info","message":"⚛️  RESET_DEVICES","pname":"renderer","timestamp":"2018-07-10T23:05:21.816Z"}

And the Nano S disconnect from Ledger Live but after some seconds it's back again.

[gre]

This should be fixed in incoming 1.0.2 , stay tuned

[bocekm]

As I mention in https://github.com/LedgerHQ/ledger-live-desktop/issues/1010, the same issue is still happening even with v1.0.2. But it's covered there, no need to reopen this one.

[infestdead]

I'm on v1.0.3 - Issue is still present.

[meriadec]

@infestdead what about v1.0.5 (still in prerelease, here https://github.com/LedgerHQ/ledger-live-desktop/releases/tag/v1.0.5)

[infestdead]

Still happening - the error message has changed.

[meriadec]

Can you try compiling the app on your side?

[infestdead]

Same error, different fonts.

[infestdead]

Any updates here? For me Ledger wallet is not usable at the moment - the chrome app now redirects to LedgerLive - but LedgerLive doesn't work with BTC/BCH/DASH - so how can I use my coins at the moment? I'm out of ideas.

[infestdead]

Updated to 1.1.2m issue is still here.

[meriadec]

@infestdead there is actually a problem with Fedora 28 (see here), probably due to openssl different implementation. Can you try on another distro?

[ETE1712]

I can’t add my account. I get an error

[gre]

@ETE1712 Please reach to our tech support

[ETE1712]

Can you please call me back

[ETE1712]

Can you please call me back?

Op ma 24 jun. 2019 om 08:57 schreef Gaëtan Renaudeau <
[email protected]>

@ETE1712 https://github.com/ETE1712 Please reach to our tech support

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LedgerHQ/ledger-live-desktop/issues/950?email_source=notifications&email_token=AMNZUBFXCMKJ6QHIL3LVCMDP4BV6XA5CNFSM4FI7BZY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYL6TZQ#issuecomment-504883686,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMNZUBCUG2D7MCAAPY3EULTP4BV6XANCNFSM4FI7BZYQ
.

>

Sent from Gmail Mobile