Nothing Special   »   [go: up one dir, main page]
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[gnokey] Ledger device not found #2737

Open
leohhhn opened this issue Aug 28, 2024 · 1 comment · May be fixed by #2928
Open

[gnokey] Ledger device not found #2737

leohhhn opened this issue Aug 28, 2024 · 1 comment · May be fixed by #2928
Labels
help wanted Want to contribute? We recommend these issues.
Milestone
⏭️Next after mainnet

Comments

@leohhhn
Copy link
Contributor
leohhhn commented Aug 28, 2024 •
edited
Loading

Description

Using a Ledger Nano S, with the installed Cosmos app (v2.35.24), and having installed gnokey from master at commit 651f5aac3706f55aa33da06a1185fe9508cb3ec2, the following error is presented when trying to add a key from the ledger device to the gnokey keybase:

> gnokey add ledger myledgerkey
unable to create Ledger reference in keybase, LedgerHID device (idx 0) not found. Ledger LOCKED OR Other Program/Web Browser may have control of device.

The device is unlocked, not used by anything else, and the Cosmos app is open. This happens when gnokey is either installed with go install, or built with go build and ran as a binary.

As @zivkovicmilos pointed out, the only way to get this functionality to work currently is by directly doing go run on the gnokey suite, ie from the gno/gno.land/cmd/gnokey directory.

The same error presents when trying to sign with the key.
@leohhhn leohhhn changed the title [gnokey] Ledger device not found when adding to keybase [gnokey] Ledger device not found Aug 28, 2024
@zivkovicmilos zivkovicmilos added the help wanted Want to contribute? We recommend these issues. label Sep 12, 2024
@0xtekgrinder
Copy link

I am sharing my research that aren't fully successful in case someone wants to get a heads start to tackle this issue.

First of all, it seems like a really really weird bug with from my tests not difference in environment or others similar things.
I have tried to follow the stack trace to see where it all mess up and it seems to be during the discovery of the ledger devices.

The stack trace is as follows:

  • the function FindLedgerCosmosUserApp inside the cosmos@ledger-comsos-go dependency
  • the function Connect inside the zondax@ledger-go dependency
  • the function Enumerate from the zondax@hid dependency

It is this last function that returns an empty array only when building the binary, and it seems that this implementation of Enumerate doesn't gets called as I couldn't see any of the logs I added when building the binary but not when running it.

@0xtekgrinder 0xtekgrinder mentioned this issue Sep 25, 2024
Open
@wyhaines wyhaines added the hacktoberfest This might be a good issue for a hacktoberfest participant to handle. label Oct 1, 2024
@leohhhn leohhhn mentioned this issue Oct 2, 2024
Open
@clockworkgr clockworkgr linked a pull request Oct 9, 2024 that will close this issue
Open
7 tasks
@Kouteki Kouteki added this to the ⏭️Next after mainnet milestone Oct 16, 2024
@wyhaines wyhaines removed the hacktoberfest This might be a good issue for a hacktoberfest participant to handle. label Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Want to contribute? We recommend these issues.
Projects
🧙‍♂️gno.land core team
Status: Triage
🚀 main.gno.land launch 🚀
Status: TODO
Milestone
⏭️Next after mainnet
Development

Successfully merging a pull request may close this issue.

fix: enable gnokey ledger support clockworkgr/gno
5 participants
@wyhaines @Kouteki @zivkovicmilos @leohhhn @0xtekgrinder