electrum 2.0.2 erases wallet file #1108
Comments
|
I believe this is a duplicate of #1085. Please upgrade to Electrum 2.0.3 and let us know if that works. |
|
yes, please upgrade to 2.0.3 |
|
I have upgraded. Since then I have not seen the problem. To: spesmilo/electrum electrum@noreply.github.com I believe this is a duplicate of #1085. Please upgrade to Electrum 2.0.3 and let us know if that works.— |
protonn
pushed a commit
to argentumproject/electrum-arg
that referenced
this issue
Feb 15, 2019
* Fix FloatingActionButton positioning on API levels before 21 * Use pkgutil to load data files, so `electroncash` package doesn't need to be extracted on Android: Closes spesmilo#1062, which I assume was caused by the cache directory being cleared while the app was running. * Update to Chaquopy 5.0.7 (closes spesmilo#1060) * Use new Chaquopy primitive conversion methods * Use new Chaquopy container view methods * Update to Chaquopy 5.1.0 / Pin version of pycryptodomex * Use correct container interface when calling get_blockchains * Add missing lock (closes spesmilo#1109) * Don't restore UI state if process has been restarted (closes spesmilo#1057, closes spesmilo#1093, closes spesmilo#1095) * Fix "Can not perform this action after onSaveInstanceState" errors (closes spesmilo#1083, closes spesmilo#1091, closes spesmilo#1103) * Trigger onShowDialog from DialogFragment.onStart rather than Dialog.setOnShowListener (closes spesmilo#1108, and see also spesmilo#1046) * Don't show temporary files in wallet list (closes spesmilo#1102) * ImageView size is now unavailable in onShowDialog, so get QR resolution from resource instead * Catch network exceptions at top level of Connection thread (closes spesmilo#1096) * Add missing locks * Fix unit tests * Update Android license agreement hash
Toporin
pushed a commit
to Toporin/electrum-satochip
that referenced
this issue
Feb 16, 2021
* Fix FloatingActionButton positioning on API levels before 21 * Use pkgutil to load data files, so `electroncash` package doesn't need to be extracted on Android: Closes spesmilo#1062, which I assume was caused by the cache directory being cleared while the app was running. * Update to Chaquopy 5.0.7 (closes spesmilo#1060) * Use new Chaquopy primitive conversion methods * Use new Chaquopy container view methods * Update to Chaquopy 5.1.0 / Pin version of pycryptodomex * Use correct container interface when calling get_blockchains * Add missing lock (closes spesmilo#1109) * Don't restore UI state if process has been restarted (closes spesmilo#1057, closes spesmilo#1093, closes spesmilo#1095) * Fix "Can not perform this action after onSaveInstanceState" errors (closes spesmilo#1083, closes spesmilo#1091, closes spesmilo#1103) * Trigger onShowDialog from DialogFragment.onStart rather than Dialog.setOnShowListener (closes spesmilo#1108, and see also spesmilo#1046) * Don't show temporary files in wallet list (closes spesmilo#1102) * ImageView size is now unavailable in onShowDialog, so get QR resolution from resource instead * Catch network exceptions at top level of Connection thread (closes spesmilo#1096) * Add missing locks * Fix unit tests * Update Android license agreement hash
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I use electrum, it sometimes starts up with the error message "can't read wallet file", and sure, the wallet file is then 0 bytes so sure enough, it's an empty file. I'm not sure when this happens.
I've studied the behavior and it seems like each time I start electrum, the wallet file goes from xx bytes, to 0 and back to xx bytes. This also happens when I shut down electrum. I have not been able to tell when the 0 byte file is left. The file where I have observed the behavior is residing on a symlinked luks spin partition if that affects things, but I'm not sure it's exclusive for this file. Pasting in an old copy of the wallet file and starting electrum again makes it work but it is somewhat unsettling. Recreating from Seed also works but the wallet file get's lost later again.
The text was updated successfully, but these errors were encountered: