Quote from: goatpig on May 08, 2017, 12:46:54 PM

Quote

Anything i can do to get this fixed @goatpig?

Build the code yourself. This is some issue with the autotoolized version of cryptopp that relies on more SSE than older machines can handle. I'm trying to fix this for 0.96.1. For the mean time your best bet is to build 0.96 directly on your machine.

Quote

can someone help in regards to the wallet being re-imported without the unconfirmed transaction? When i tried importing it while armory is preparing databases it locked the wallets and crashed the GUI while armory was actually still scanning in the background. please someone help!!! i hope i dont lose any bitcoin because of unconfirmed transaction Huh

Import in offline mode first then sync in online mode. If you want to wipe the ZC, delete the following files in your DB folder:

Code:

zeroconf
zeroconf-lock

@goatpig
I tried doing what you said above, even in offline mode i tried to import but the gui crashes and theres nothing written in the logs about that issue.
I even deleted the zeroconf-lock files.

when i tried to import the wallet above, like i said previously i notice 2 extra files in the folder that are auto created as the crash happens:
armory_XXXX_wallet.lmdb-lock
armory_XXXX_wallet.lmdb

I dont know why these files are auto created?

I uninstalled armory 96.0 and reinstalled the old version, seeing everything sync up again, the entry that was unconfirmed is no longer there anymore which is a good thing.
The bad thing is that it doesnt seem like wallet importing works in 96.0.

Im going to recreate a new empty wallet from the old armory and try import that into the new armory and il get back to you on that.