keplr-wallet icon indicating copy to clipboard operation
keplr-wallet copied to clipboard

Cannot connect to Ledger via USB on Ubuntu

Open ChrisiPK opened this issue 1 year ago • 0 comments

Describe the bug Chromium on Ubuntu cannot connect to Ledger hardware wallet when trying to import wallets.

To Reproduce Steps to reproduce the behavior:

  1. Install Keplr extension for Chromium on Ubuntu
  2. On the post-install screen of Keplr, click 'Connect Hardware Wallet'
  3. On the next screen, click 'Connect Ledger'
  4. On the next screen, enter Wallet Name, new Keplr password, select 'Cosmos app (Recommended)', then click 'Next'
  5. Plug in Ledger Nano X via USB, unlock it and start the Cosmos app on it
  6. (optional) Select 'Use alternative USB connection method(HID)' in Keplr
  7. Click 'Next' in Keplr
  8. Chromium shows a prompt to select the USB device to connect to. Select the Ledger device and confirm.
  9. Nothing happens. User is stuck on the 'Please connect your Hardware wallet' screen in Keplr. Clicking the next button does not have any effect.

Expected behavior After step 8, Keplr should establish a connection to the Ledger device and continue with the import process.

Screenshots screen-capture.webm

Device details (please complete the following information):

  • OS: Ubuntu 22.04.3, kernel 5.15.0-91-generic
  • Browser: Chromium Version 120.0.6099.71 (Official Build) snap (64-bit)
  • Keplr Version: 0.12.50
  • Hardware Wallet: Ledger Nano X, secure element version 2.2.3, microcontroller version 2.30, bootloader version 1.16, Cosmos app version v2.34.12

Additional context Works fine on Windows and Chrome. Since Chromium is installed via Snap, I also tried adding the raw-usb capability to the snap, but it didn't change the behavior.

Only this error message is visible on the console: Error: <svg> attribute width: Expected length, "auto".

Tried this also on another machine with a newer ubuntu version, but same issue. Let me know if you need to have detailed version info for the other machine as well.

Ledger Live was NOT running during this operation, as some people mention that it might cause issues when it tries to access the Ledger device simultaneously with the browser.

ChrisiPK avatar Dec 15 '23 00:12 ChrisiPK