-
Notifications
You must be signed in to change notification settings - Fork 301
Device not detected on Ubuntu #1220
Comments
Can you add udev rules as described in that help section: Connection issues with Windows or Linux? See also: #1057, we will display a link to the article inside the app to help in those cases. |
I had the exact same issue, adding the udev rules solved it, thanks 😄 |
Having the same problem but adding the udev rules haven't resolved it for me. I've added both the rules for the subsystem and the kernel, even after $ uname -a
Linux samus 4.17.8-1-ARCH #1 SMP PREEMPT Wed Jul 18 09:56:24 UTC 2018 x86_64 GNU/Linux
$ stat ./ledger*
File: ./ledger-live-desktop-1.0.3-linux-x86_64.AppImage
Size: 81840061 Blocks: 159856 IO Block: 4096 regular file
Device: 802h/2050d Inode: 820047 Links: 1
Access: (0755/-rwxr-xr-x) Uid: ( 1000/christianbundy) Gid: ( 1000/christianbundy)
Access: 2018-07-23 11:51:57.503338804 -0700
Modify: 2018-07-23 11:50:26.823338042 -0700
Change: 2018-07-23 11:51:56.173338793 -0700
Birth: -
$ ./ledger-live-desktop-1.0.3-linux-x86_64.AppImage
Checking for update
Update for version 1.0.3 is not available (latest version: 1.0.3, downgrade is disallowed).
dev 2c97 / 1 : usage_page:3a32, usage:2e31
dev 2c97 / 1 : usage_page:3a32, usage:2e31
dev 2c97 / 1 : usage_page:3a32, usage:2e31
dev 2c97 / 1 : usage_page:3a32, usage:2e31
[above output continues repeating until app closes] Please disregard, I had to add |
I am still having this problem in Fedora28. Cant get pass "Navigate to the dashboard on your device" stage. I have added udev rules, added owner="usrname" and even the last suggestion here:
Any other way to make this work on my Linux machine? This is an already initialized [on Windows] Nano S |
@leyei Can you copy and paste your full udev rules here? Also, can you verify that you've run the below commands after making the changes?
|
Thanks @christianbundy. Here is what I have under 20-hw1 for now
|
fedora 28 removed the group "plugdev". I changed the rules from GROUP="plugdev" to OWNER="MYUSERACCOUNT". But I still cannot verify my devices. |
Thanks @cnu80 for that clarification. So I think this solution wont work for Fedora28. Will there be a fix from Ledger that will make it possible to use Ledger Live on Linux smoothly? |
Ye, that's the goal, but you know there is multiple differences across distributions ;) At first, builds were done on Arch, then Ubuntu 18, then (latest build) has been done on Ubuntu 16.04 to be as compatible as possible (dylibs problems..). The optimal will be to push build scripts directly on distribution repositories (already done for Arch Linux). So keep updated, and sorry for the inconvenience! |
Finally @meriadec! Thanks for this clarification. Apparently we will have to wait for a Ledger Live application that works on major Linux distros or package management systems they're based on. Example, you could just work on debian-based, RPM-based, Pacman-based and Gentoo-based. This should cover majority of Linux users out there. |
@leyei You can drop the
And then: sudo udevadm trigger && sudo udevadm control --reload-rules If that doesn't work I might increase the logging with: udevadm control --log-priority=info Or you can read the logs directly with: udevadm monitor --environment Hopefully the logs give us enough info that we can get this working on your system! |
Thanks @christianbundy ! Now I can get pass this stage by adding Unfortunately, I am getting new error already reported 950 and 1010 This problem only comes when trying to add cryptos identical to Bitcoin i.e. Litecoin Ł - LTC, Bitcoin Cash - BCH & also Bitcoin ₿ - BTC |
Now my Ledger S is working on Fedora 28. I changed my udev rule from group to owner and replaced my USB cable. With the old usb cable it was not possible to verify my ledger device. Now I am waiting for the Bitcoin/Dash fix. Thanks for your great work !!! Is a flatpak version also planned? |
Just tested on fresh Fedora 28 install, adding udev rules as described in the help documentation resolve the problem (see #1220 (comment) and https://support.ledgerwallet.com/hc/en-us/articles/115005165269-Fix-connection-issues) |
In my case, it turns out that I was using a USB cable with no data pin... See no events at all with |
I had same problem on Ubuntu 16.04.
I had not this lib supported on my system. Check: Then I've install this llib:
This work for me. |
Ledger Live Version and Operating System
Expected behavior
After recognizing the device it asks to browse to the dashboard of device.
It should recognize the device is on the dashboard.
Actual behavior
It never recognizes the device is on the dashboard.
Steps to reproduce the behavior
-open Ledger Liver
-Verify Device
-Connect Device
-Navigate to dashboard (on Device)
The text was updated successfully, but these errors were encountered: