How to make WSL work?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- embedded-iot, operating-systems
Research direction
Reproduce the shown Python command under WSL and start at ledgerblue/comm.py, where getDongle raises the reported exception. Check how the Ledger device is exposed to WSL and identify what is needed for the command to detect it; done means the dongle is detected or the WSL limitation and workaround are documented.
Written by the indexing model from the issue text.
Description
Hi,
I am using WSL (Windows SubSystem for Linux), and it always complains "no dongle found", please could you advice how to fix this?
python3 -m ledgerblue.loadApp --targetId 0x31100003 --fileName bin\app.hex --icon 0100000000ffffff0000000000fc000c0f3814c822103f101120092005400340018001800000000000 --curve secp256k1 --path "44'/195'" --apdu --appName "Tron" --appVersion "VERSION_NUMBER" --appFlags 0x40 --delete --dataSize 145311 --tlv
Traceback (most recent call last):
File "/usr/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/usr/local/lib/python3.8/dist-packages/ledgerblue/loadApp.py", line 199, in <module>
dongle = getDongle(args.apdu)
File "/usr/local/lib/python3.8/dist-packages/ledgerblue/comm.py", line 240, in getDongle
raise CommException("No dongle found")
ledgerblue.commException.CommException: Exception : No dongle found
- Dominant language
- Python
- Stars
- 125
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LedgerHQ/blue-loader-python
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
LedgerHQ/blue-loader-python#130 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
LedgerHQ/blue-loader-python#111 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
LedgerHQ/blue-loader-python#98 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
LedgerHQ/blue-loader-python#96 · 4 comments · 3 reactions ·
-
installation hintsOpen
Difficulty 1/5 Under an hour Newbie friendliness 55/100
LedgerHQ/blue-loader-python#76 · 1 reaction ·
All issues in LedgerHQ/blue-loader-python
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PedestrianDynamics/pyFDS-Evac#199 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
521xueweihan/HelloGitHub#3790 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sandialabs/atlas-ui-3#978 ·
Maintainers usually reply within 1 day
-
area: tests perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Nitjsefnie-Harness-Commons/daedalus#1255 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4256 ·
Maintainers usually reply within 1 day