Exception: no seed or master_key in data
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
Traceback (most recent call last):
File "electrum\gui\qt\wizard\wizard.py", line 217, in on_next_button_clicked
File "electrum\gui\qt\wizard\wizard.py", line 229, in submit
File "electrum\wizard.py", line 74, in resolve_next
File "electrum\wizard.py", line 353, in maybe_master_pubkey
File "electrum\wizard.py", line 442, in keystore_from_data
Exception: no seed or master_key in data
Exception: no seed or master_key in data
Reporter
This issue was reported by 8 user(s):
| Electrum Version | Python Version | Operating System | Wallet Type | Locale | Stack |
|---|---|---|---|---|---|
| 4.5.4 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | en_US | ℹ | |
| 4.5.4 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.22631-SP0 | en_US | ℹ | |
| 4.5.8 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | fr_FR | ℹ | |
| 4.5.8 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | fr_FR | ℹ | |
| 4.5.8 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | fr_FR | ℹ | |
| 4.5.5 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.22631-SP0 | en_US | ℹ | |
| 4.5.5 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | imported | ru_RU | ℹ |
| 4.5.8 | 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:20:04) [MSC v.1929 32 bit (Intel)] | Windows-10-10.0.19045-SP0 | imported | en_US | ℹ |
Additional Information
authentification
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with the traceback in electrum/gui/qt/wizard/wizard.py and follow the calls into electrum/wizard.py, especially resolve_next, maybe_master_pubkey, and keystore_from_data. Reproduce the reported wizard flow if possible using the crash details, then determine why the data lacks a seed or master_key. Done means the flow completes without this exception and the regression is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100