[gnokey] Ledger device not found

[leohhhn]

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.

[0xtekgrinder]

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.