--rebuild does not work.
Deleted .armory directory, started armory again (latest testing branch from a few minutes ago) with this result:
laptop:~/Downloads/armory/BitcoinArmory$ python ArmoryQt.py
********************************************************************************
Loading Armory Engine:
Armory Version: 0.89.99.6
PyBtcWallet Version: 1.35
Detected Operating system: Linux
OS Variant : ('Ubuntu', '13.04', 'raring')
User home-directory : /home/xxx
Satoshi BTC directory : /home/xxx/.bitcoin/
Armory home dir : /home/xxx/.armory/
LevelDB directory : /home/xxx/.armory/databases
Armory settings file : /home/xxx/.armory/ArmorySettings.txt
Armory log file : /home/xxx/.armory/armorylog.txt
Log file doesn't exist [yet]
(WARNING) armoryengine.py:11197 - Overriding not-available message. This should happen 0-5 times
-INFO - 1382477339: (BlockUtils.cpp:1582) Set home directory:
-INFO - 1382477339: (BlockUtils.cpp:1604) Set blkfile dir: /home/xxx/.bitcoin/blocks
-INFO - 1382477339: (BlockUtils.cpp:1614) Set leveldb dir: /home/xxx/.armory/databases
-INFO - 1382477339: (BlockUtils.cpp:1570) SetBtcNetworkParams
-INFO - 1382477339: (BlockUtils.cpp:3542) Executing: doInitialSyncOnLoad
-INFO - 1382477339: (BlockUtils.cpp:3582) Number of registered addr: 0
-INFO - 1382477340: (BlockUtils.cpp:1709) Current Top block in HEADERS DB: 0
-INFO - 1382477340: (BlockUtils.cpp:1710) Current Top block in BLKDATA DB: 0
-INFO - 1382477340: (BlockUtils.cpp:1711) Current Applied blocks up to hgt: 0
-INFO - 1382477340: (BlockUtils.cpp:3606) Clearing databases for clean build
-WARN - 1382477340: (BlockUtils.cpp:3507) Destroying databases; will need to be rebuilt
pthread lock: Ongeldig argument
Afgebroken (geheugendump gemaakt)
Question: how can I make a fresh Armory restart?
Ack, this is really not going well on Ubuntu 32-bit (that's what you're in, right?). You can remove the /home/xxx/.armory/databases directory to retry from scratch. Though, "--rebuild" should do exactly that.
I noticed the line "pthread lock: Ongeldig argument", I assume that means "Invalid Argument"? If so, that may be the source of the problem, perhaps the way leveldb is being compiled here is not playing nicely with the 32-bit libraries.