spesmilo / spesmilo/electrum

Electrum fails to open wallet file from a Cryptomator volume with capital letter in the path

Open
#5,987 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

OS-windows 🪟
Dominant language
Python
Stars
8.6k
Forks
3.5k
Avg merge
2d 8h
Merged PRs (30d)
61

Description

Title:
Electrum fails to open wallet file from a Cryptomator volume with capital letter in the path

Description:
On Windows, Electrum fails to open (browse) existing&valid wallet file from an unlocked Cryptomator volume when the path contains a Capital letter (at any position).

Details:
Drive D: - physical SSD, not encrypted
Drive V: - Cryptomator, Dokany/Dokan, encrypted, unlocked drive

D:\lowercase\wallet - works
D:\Uppercase\wallet - works

V:\lowercase\wallet - works
V:\Uppercase\wallet - Doesn't work (This file does not exist message is shown)
V:\withCapital\wallet - Doesn't work (This file does not exist message is shown)
V:\lowercase\capitalInpath\wallet - Doesn't work (This file does not exist message is shown)

Additional information:
Windows 7 x64 (fully patched)
Cryptomator 1.4.15 (latest)
Electrum 3.3.8 (latest, installed)
wallet - Standard, encrypted

While in the mounted/decrypted state, Cryptomator volume shows as Cryptomator File System:

image

The How it works section of dokany describes the file system implementation in more detail:

Steps to reproduce:

  1. Install Cryptomator on Win7 x64
  2. Create a new Dokany vault
  3. Unlock Cryptomator volume
  4. Create a new Electrum encrypted wallet
  5. Close Electrum
  6. Create "Uppercase" folder on the Cryptomator volume
  7. Copy Electrum wallet into "Uppercase"
  8. Start Electrum and browse to the wallet on the Cryptomator volume (section 7)
  9. This file does not exist message will show

Screenshots:
image

image

image

Edit:
Added more info about dokany

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files, tests, or entry points. Start by reproducing the browse failure on a Cryptomator/Dokany volume with a capitalized path, then trace the wallet file selection and path-existence check; done means an existing wallet opens successfully from that path.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.