Ledger-live-desktop: 2.19 on linux buggers up ledger live

[serejandmyself]

Installed 2.19 on linux. Cant access the manager anymore. It just keeps recommending i fix the ledger. The device works perfectly. All the installed apps keep working as should...

Please fix the manager access

EDIT: for anyone stuck with the issue, download live .17 Works just fine

[gre]

When you mention specifically the version 2.19, do you mean it was working in 2.18 🤔
Does only the Manager fail to access? Or add accounts / send / receive as well?

For Linux, you might need to make sure you have set up the udev rules https://github.com/LedgerHQ/udev-rules/blob/master/add_udev_rules.sh

[serejandmyself]

I will re-describe. Ledger itself is working fine. Prior to 2.19 Ledger live was working fine. No need to update udev rules, as Ledger is working fine.

Starting with version 2.19 on linux Ledger live does NOT work. It does not see the Ledger device. The device itself keeps on working with the apps it has installed on it. But i cant use ledger live to update it, send, access manager, etc

I am unsure about 2.18. I updated straight from 2.17. Prior to this version, it was all good. The issue is the connection to ledger live on linux at 2.19

@gre

[kvittenera]

It's the same for me. It worked with 2.18 and version 2.19 cannot detect the stick anymore. Nothing else changed.
Unfortunately version 2.18 is not available any longer...

[gre]

Ok, i'm sorry this is happening :(

All our past releases are still available on https://github.com/LedgerHQ/ledger-live-desktop/releases (and signatures can always be checked on https://ledger-live-tools.now.sh/lld-signatures )

Technically, what I can see is that we have upgraded node-hid library in order to upgrade our Electron version in the future. (ctx https://github.com/node-hid/node-hid/issues/398 thx to help from @todbot )

On our side, we were able to make this work on Linux under a few distribution and didn't found this issue so I'm curious where the problem is. We might move forward to Electron 11 + even more recent node-hid (which upgraded latest hidapi) to see if it helps fixing this, otherwise we need to dig more into where the problem is exactly (we might need more precise logs – after a Ctrl+E logs can be viewed using https://ledger-live-tools.now.sh/logsviewer otherwise send them to our techsupport but don't send them here if you have accounts in your Live for privacy reason ).

cc @valpinkman in context of Electron 11 upgrade. we should to upgrade node-hid in ledgerjs too.
cc @Arnaud97234 / @nabil-brn : if you guys find a way to reproduce and extract the logs.

(i'm holidays for 2 weeks and part of the team will be off during Christmas but I hope we fix this in January)

[serejandmyself]

That's a strange solution to leave users stranded for 2-3 weeks, because of a religious holiday (assuming most of your users do not celebrate it). If it worked on your end it doesn't mean it works (period). The worst developing mistakes one can do is to say it works on my end... Well, as of now - it doesn't. Short story, don't release, properly, untested software. I appreciate your quick answers, but it's a shame that this is what you propose.

For anyone stuck with the same issue, download and use (live) 17.1, it seems to mess up balances, but at least I am able to conduct transfers and install / delete apps.

[gre]

My point is precisely that we tested on Linux and didn't see any issue so we can't say it's untested...

So any help is appreciated to understand the problem. Part of the team is still available, the Ledger Live team is small, this is open source too so feel free to help. We are on GitHub here.

[gre]

We are able to see that Ubuntu 18.04 have the issue but not Ubuntu 20.04. relates to version of libstdc++6.

[gre]

more clarification:

• the issue is in fact related to the Linux version we built on. This latest Linux build only supports very recent versions of Linux distributions (like Ubuntu 20.04) but broke older.
• we should be able to fix the issue in our next build, we will make sure to be backward compatible with older distribution. Our next build is likely to be mid January tho. (we have workaround in the meantime: either use 2.17, or use the CI build, or build it yourself)
• Typically, if you take the CI build (equivalent of the 2.19.0 we published) https://github.com/LedgerHQ/ledger-live-desktop/actions/runs/427842994 it actually works properly even on older Linux. We will improve the way we build our releases and make sure this no longer reproduce.

[serejandmyself]

Im unsure as to why all these words... As someone who has been in the industry for over 5 year, imo, its a shame you just cant see the issue of trying to defend the release of software witch wasnt properly tested. But i dont think the bug is the issue here. And i didnt when i posted it. I think the response we tested, it wasnt there, etc - thats the issue. I any case, seems like further disillusion of the topic is irrelevant to the bug

[todbot]

@serejandmyself it's difficult to test hardware-based apps across the many different distros and versions of Linux. I'm surprised Ledger isn't just saying "only works on Ubuntu 20.04". As for "all the words", to me this sounds like standard recording in this issue report where the problem may be, for figuring out how to fix it when the team gets back from holiday. This whole year has been terrible, cut folks some slack.

[gre]

We test all our releases under at least latest Linux distribution (typically Ubuntu) and I was just being transparent about that.
Github issues discussion is used to investigate the actual problem. Going meta in this discussion is not productive and is not helping on the actual issue..
Indeed we didn't see this issue because we don't test on older Linux versions, something we can improve for the next time but as @todbot it's not something easy to do (especially this happens at the time you use the hardware device, so it's something that would require us to test on much more computers, we plan to have more QA force over 2021 to help on that + reinforce our beta program to try to detect such issues ahead of time).

So indeed after more internal discussion we quickly figured out it was related to the targetted glibc++ version. Expect our next release to fix the problem.
Thanks

[serejandmyself]

@serejandmyself it's difficult to test hardware-based apps across the many different distros and versions of Linux. I'm surprised Ledger isn't just saying "only works on Ubuntu 20.04". As for "all the words", to me this sounds like standard recording in this issue report where the problem may be for figuring out how to fix it when the team gets back from holiday. This whole year has been terrible, cut folks some slack.

As I mentioned, I have no issue with anything, other than the we tested - it works sentence. We are software builders here and imo, we should strive to make experience better. Saying its tested - its not our fault isnt that imo.

I mean guys. you still didnt ask me what version of Ubuntu im using (16.04) or to provide my logs, etc. I think that discussing the bug should be the main concern. Thanks

[gre]

I never said "we tested, it works". I don't understand where you think I had this mindset in that message: https://github.com/LedgerHQ/ledger-live-desktop/issues/3408#issuecomment-750284188. My intention was not to close the investigation, on the contrary I was curious to know about more information.

On our side, we were able to make this work on Linux under a few distribution and didn't found this issue so I'm curious where the problem is.

Indeed I just wanted to point out that, as all our releases, our QA team did make that build works on Linux, and therefore we didn't detect the problem. (so in a sense, that info is useful because indeed it only breaks in older version after further investigation)

it helps fixing this, otherwise we need to dig more into where the problem is exactly (we might need more precise logs – after a Ctrl+E logs can be viewed using https://ledger-live-tools.now.sh/logsviewer otherwise send them to our techsupport but don't send them here if you have accounts in your Live for privacy reason ).

^ This is where I asked for logs.

I also initially thought it was node-hid but it's not, it's purely in the way we did this build, we probably upgraded our Linux version which broke older distribution support when doing the build on it.

[LouisLoudogTrottier]

CentOS, same issues sine 2.19, tried Nano S and Nano X, Same behaviour as everyone else here. Cannot «Connect and Unlock via USB». Nano X works as expected on Android App. Everything working fine before update. All other USB device work as usual.

Ledger device on Ledger Live AppImage 2.19 are broken but works just fine with 2.18 as 2020-12-23 22:37

[mgagliardo]

Same issue, Debian latest release (buster), Ledger Nano S with latest firmware. Working in v2.18.0 but not being recognized in v2.19.0, same cable and same notebook device.

[TonyErnesto89]

Same issue for me. Distro based on Ubuntu

[roycocup]

May I suggest that if automated tests on different platforms are not easy to do, maybe we can have the community beta-test them before deploying a production version?

I understand that its hard to test hardware on multiple platforms. Maybe you can test 10 different ones, but there will be several combinations of OS's and machines that may cause problems as well.

What you can do is use the sheer number of community members who would probably be more than happy to test that for you, in exchange for crediting their name as beta testers and thus avoid the bad publicity.

[jimbowarrior]

same issue with Debian 10, I open Ledger live with full access/functionality. I finally upgraded to 2.19 and my Ledger nano X is not recognize anymore but it working on windows or from android app. So please take in consideration is related to you last version ....

[dnmon]

Debian should be the distro for testing an application which claims to be linux supported. Seeing others here using buster as I am, confirms my view. Besides, going through this thread gives me a good impression of competence and commitment level of the Ledger team. The recent failures on top, makes me question the safety and trust in the product.

[jimbowarrior]

Debian should be the distro for testing an application which claims to be linux supported. Seeing others here using buster as I am, confirms my view. Besides, going through this thread gives me a good impression of competence and commitment level of the Ledger team. The recent failures on top, makes me question the safety and trust in the product.

same here ....

[cobordism]

Confirmed for QubesOS with debian 10 template.
2.18 works, 2.19 does now. I had to downgrade.

[greenknot]

If it can help, this temporary workaround works for me on Ubuntu 18.04.5 LTS:

#!/bin/bash

set -e

DEBFILE='libstdc++6_10.2.0-5ubuntu1~20.04_amd64.deb'
LIBFILE="usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28"
TMPDIR="/tmp/ll-3408"

if [ $# -ne 1 ]; then
    echo "Usage: $0 </path/to/ledger-live-desktop-2.19.0-linux-x86_64.AppImage>"
    exit 1
fi

mkdir -p "$TMPDIR"

if [ ! -f "$TMPDIR/$DEBFILE" ]; then
    wget -q "http://security.ubuntu.com/ubuntu/pool/main/g/gcc-10/$DEBFILE" \
         -O "$TMPDIR/$DEBFILE"
fi

echo "5b925f79c1a4f4095b173cce456173508c9fc763b5584acc05f8ba8c4ceb32d3  $TMPDIR/$DEBFILE" \
    | sha256sum --check --quiet -

if [ ! -f "$TMPDIR/$LIBFILE" ]; then
    (cd "$TMPDIR" && ar x "$TMPDIR/$DEBFILE" data.tar.xz)
    tar -C "$TMPDIR" \
        -xf "$TMPDIR/data.tar.xz" \
        ./usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28 \
        ./usr/lib/x86_64-linux-gnu/libstdc++.so.6
fi

export LD_LIBRARY_PATH="$TMPDIR/usr/lib/x86_64-linux-gnu"
"$1"

[mgagliardo]

Debian should be the distro for testing an application which claims to be linux supported. Seeing others here using buster as I am, confirms my view. Besides, going through this thread gives me a good impression of competence and commitment level of the Ledger team. The recent failures on top, makes me question the safety and trust in the product.

+1, gonna test some other products out there :)

[MihailYotov]

I can confirm that 2.18 and previous works on Ubuntu 16.04 and 2.19 not. Great time to be unable to use the Leader, don’t you think?

[brkroot]

2.19 was working like a charm on 18.04 till decided to change the login password few days ago (6th Jan) , and since then can't connect with the ledger that is still with 1.6.0 fw by the way.
Tried older versions of ledger live as well as on windows with no success.

Did not tried to reset the device and set it as new, is it even worth the try?
I think distros or other systems and compatibility are not the only issue, its just the latest update messed up with the older firmwares and that's why just my the device is not connecting in any way on any system

Although the device itself seems fine and the apps that were installed.

[gre]

Ledger Live v2.20.0 have fixed the problem.
https://github.com/LedgerHQ/ledger-live-desktop/releases/tag/v2.20.0

v2.20.0 is still a pre-release but is planned to be released next Monday.
Thanks.