search

antichris / ledobe

Build Ledger Live components in an isolated Docker environment with persistence between sessions.
Mozilla Public License 2.0
7 stars 4 forks source link

Unable to connect nano x to ledger live #3

Open zyrorl opened 3 years ago

zyrorl commented 3 years ago

Firstly the appimage doesn't run for me, says libz.so is missing.

When running the unpacked ledgerlive package, it simply won't connect to the ledger.

Also i've noticed the version of ledger is older than the current release, so maybe contributing to the problem?

antichris commented 3 years ago

#

Firstly the appimage doesn't run for me, says libz.so is missing.

You're missing zlib. Just install it using the method you normally use to install system dependecies/packages on your system (e.g. apt, packman, yum, compile from source, etc.)

won't connect to the ledger

Yeah, this is a known problem and Ledger Live support site offers tips on dealing with it. I tried most, if not all, of them on the initial release trying to get a Raspberry Pi 4B (running the ARM64 RaspPi OS 2021-04-09 release) to cooporate, but no joy. Another user was successful on his (non-'berry) device though, so looks like it's YMMV.

the version of ledger is older than the current release, so maybe contributing to the problem

It may very well be. I don't have the time and resources avaliable at the moment to look into this, but you're very welcome to submit a PR if you manage to tackle it.

Here's a patch to get you started. ```diff diff --git a/docker/build/Makefile b/docker/build/Makefile index 5d4f262..5a24cf5 100644 --- a/docker/build/Makefile +++ b/docker/build/Makefile @@ -14,9 +14,9 @@ ifdef SHVERBOSE endif ## TODO Rebuild when any of the versions change. -vDesktop := 2.26.1 -vCoreLib := 3.5.4 -vCoreNPM := 6.11.3 +vDesktop := 2.32.2 +vCoreLib := 661687f805f7d447ec5e9aeb010a805ae53744ff ## "3.5.0-rc-661687" +vCoreNPM := 6.12.5 dirRoot := ${PWD} dirDesktop := ${dirRoot}/desktop ``` If you do manage to get it working, or, at least, building successfully, please report back here and I'll do a new release.
antichris commented 3 years ago

Hey, @zyrorl, what's your progress? Did those support instructions work for you? Did you apply the patch? Or did you find another solution?

zyrorl commented 2 years ago

Hey @antichris, sorry it was a while since I had tried it to no avail. I have recently re-attempted it with some level of success.

I have basically been able to build it using vDesktop=2.36..3 vCoreLib=4.1.2 vCoreNPM=6.14.5

The result is however that when trying to add certain crypto currencies like Bitcoin, Tron, etc that rely on CoreLib it seems to fail with a "process killed by SIGABRT" error. Ethereum, Stellar, and Tezos seemed to add just fine.

I've tried downgrading to past versions of Corelib with no success. So i'm not sure what exactly is going on, or even how to debug it at this point.

antichris commented 2 years ago

I'm glad to hear, @zyrorl, that you did have some success (albeit limited) after all.

vCoreLib=4.1.2

That's interesting. It really is the latest version they have actually publicly tagged, but their Node bindings version 6.14.5 points at an untagged commit as "4.2.0-rc-845b1b" (and has done so since June), and they use the corresponding compiled .so file from their servers when building this version of Node bindings. Oh, well, I guess it's just their usual mess.

I just released the latest version of the build environment, it would be really cool if you could take it for a spin and pop back in here to tell how it went. Without an ARM64 device I'm kind of flying blind here.

(lib-ledger-core-node-bindings/package.json at 6.14.5 · LedgerHQ/lib-ledger-core-node-bindings)
(Merge pull request #794 from LedgerHQ/hzheng-ledger-patch-1 · LedgerHQ/lib-ledger-core@845b1b6)
(new version of libcore · LedgerHQ/lib-ledger-core-node-bindings@5154900)
(lib-ledger-core-node-bindings/preinstall.js at master · LedgerHQ/lib-ledger-core-node-bindings)
(Release 0.2.0 · antichris/ledobe)
antichris commented 2 years ago

their Node bindings version 6.14.5 points at an untagged commit as "4.2.0-rc-845b1b"

To make things more fun, in addition to 6.14.5 they also have v6.14.5 (spot the difference?), that points to an different commit and uses an entirely different core lib version (3.5.0-rc-661687).

The latest release deals with this ambiguity and, in theory, should build more stable artifacts on par with the official x64 builds. I suggest you check it out and report back whether you had any issues with it.