To remove factors, I tried again:
- removed all wallets, ArmoryQt starts fine in online mode
- created a new wallet, it's online immediately
- shut down Qt and DB
- started Qt, created a new wallet with password, nothing else changed or touched (in offline mode)
- shutdown Qt
- started DB, then Qt
- Qt starts scanning
(INFO) ArmoryQt.py:4673 - Dashboard switched to "Scanning" mode
(python:14412): Gtk-CRITICAL **: IA__gtk_progress_configure: assertion 'value >= min && value <= max' failed
"Scanning" comes around every 5 secs, that Gtk warning came only once. Nothing else for an hour scanning.
At "35 sec left", the last DBlog.txt line is
-INFO - 12:29:15: (BlockchainScanner.cpp:852) scanned from block #514744 to #515526
(which is not the current blockheight)
and Qt says
-ERROR - : (BinaryData.h:563) odd hexit count
over and over.
After restarting Qt, I can't connect to DB any more, I have to restart the service.
tl;dr: a single fresh plain wallet, nothing changed, nor commented, and Qt hangs.Oh, maybe it has something to do with a recent upgrade to Debian 9? I probably didn't import/rescan since then.
But I did install/compile v0.96.4, which threw no errors.
Ente
Send me one of those fresh, broken wallets.