LedgerHQ / udev-rules

udev rules to support Ledger devices on Linux
Apache License 2.0
106 stars 38 forks source link

Udev rules don't work on Ubuntu 21.10 #12

Open billytetrud opened 2 years ago

billytetrud commented 2 years ago

My user is also apart of the plugdev group, but no love. Eg attempting to connect my trezor at https://adalite.io/ does not recognize the device after I put my pin in.

billytetrud commented 2 years ago

FYI, I have not gotten this fixed. A colleague on Ubuntu 20.04.3 LTS had a working ledger until upgrading the firmware. It seems likely this is a firmware bug and unlikely a udev rules change would help. FWIW I tried adding this kind of stuff to the udev rules: https://forum.electro-smith.com/t/web-programmer-securityerror-access-denied-on-linux-solved/192 which I noticed Trezor's rules have, but didn't help (also didn't hurt - ledger live could still connect fine).

maximlomans commented 1 year ago

i ve used ledger-live for two years on Win7 no problem, though since the latest upgrade to both version 2.49.2 & 2.50 i ve had no luck reaching nano - I've removed all previousley installed drivers and reinstalled both apps on Win and Linux hosts, both have failed to detect nano - luckily though the mobile version still works .. for how long though im not sure .

Ubuntu 22.04

Ledger Live 2.50.0 [159212:1202/175947.259671:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. spawned internal process 159259 init Checking for update Generated new staging user ID: c1f163fd-6e74-5ce1-9de3-9bd985f09a4c Update for version 2.50.0 is not available (latest version: 2.50.0, downgrade is disallowed). ending process 159259 ... internal process 159259 gracefully exited with code 0 [159212:1202/180122.476783:ERROR:node_controller.cc(567)] Trying to re-add dropped peer 69E2449D702F25B1.8E9C92D021D34C41

$ cat ledgerlive-logs-2022.12.02-18.00.55-9a329e7.json

...."✖ CMD connectManager error","pname":"renderer","timestamp":"2022-12-02T17:00:49.922Z"},{"type":"cmd.ERROR","data":{"name":"CantOpenDevice"},"level":"warn","message":"✖ CMD connectManager error","pname":"internal","timestamp":"2022-12-02T17:00:49.918Z"},{"error":{"name":"CantOpenDevice"},"level":"warn","message":"Command error:","pname":"internal","timestamp":"2022-12-02T17:00:49.916Z"},{"type":"hid-verbose","message":"new HID transport","level":"debug","pname":"internal","timestamp":"2022-12-02T17:00:49.914Z"},{"type":"promise-retry","message":" failed. 1 retry remain. TypeError: cannot open device with path /dev/hidraw1","level":"debug","pname":"internal","timestamp":"2022-12-02T17:00:48.896Z"},{"type":"hid-verbose","message":"new HID transport","level":"debug","pname":"internal","timestamp":"2022-12-02T17:00:48.895Z"},{"type":"promise-retry","message":" failed. 2 retry remain. TypeError: cannot open device with path /dev/hidraw1", .....

https://wiki.archlinux.org/title/udev :

"udev's main purpose is to act upon peripheral detection and hot-plugging, including actions that return control to the kernel, e.g., loading kernel modules or device firmware. Another component of this detection is adjusting the permissions of the device to be accessible to non-root users and groups.

As the successor of devfsd and hotplug, udev also manages device nodes in the /dev directory by adding, symlinking and renaming them. udev replaces the functionality of both hotplug and hwdetect. "

maximlomans commented 1 year ago

I found something Ubuntu has Ledger's udev rules in its repo

have yet to install em & run the app.... but in tthe meantime you could do the same

maximlomans commented 1 year ago

It Worked !