Thanks. According to the log the tx has "used already spent key images".

I'm going to follow the steps set out here (assuming they are still valid):


Silly question but where can the wallet .bin file be found on Mac OS X? There is a file with the same name as the wallet in the user/[username] directory however the file doesn't have an extension. Should I be moving/ renaming this?

Ah yes thanks... I remember now (it's been almost two years since I last created one!)

This is nearly as bad as if you find out some douchebag lawyer or government goon has put a hold on your bank account.  I would like to request that Monero include this information in an easy to find place, say in a readme file with the client download, or prominently displayed in the first post of this thread. Also, it would be nice to know what if anything a person that has in a wallet for the previous version needs to do or doesn't need to do to make their wallet work with the new version.  A couple of times it seemed ridiculous to even find anything telling you anything.  

Also it seems that the daemon does not want to close sometimes.  If you are synching and trying to close before the synching finishes, it hangs there and you don't have a clue what is going on.  If you type exit again it takes a while and does close.

Also, it would be nice to know that your coins are good without having to send them to another wallet or some other strange way to just see if the new code has destroyed your coins.  Some of us don't like to have to babysit the coins in a way that you have to do it just to see if you could even send them.  

I hope monero goes to $20,000 per coin so I can be rich.

Just my .02 Moneros.

Ok, so you may need to run "rescan_spent" in simplewallet as well as the above steps. I'd recommend just running "flush_txpool" in the daemon console first (and resending the transaction) before trying any of the above.

Great thanks this worked. Only I refreshed the wallet, rather than rescanned. Didn't wait 24hrs though (life's too short).

The scanning is in the background now. You don't have to wait for it, but newly received coins won't appear right away, until the scan reaches them.

The bug is inherent to the 9.1 version of Hydrogen Helix and is patched in 9.3 already. Therefore, I think it's a bit redundant to include it in the documentation.

Latest monero wallet 0.9.3 works fine with cyrillic password (just made a new wallet and tested it). Old Jojatekok wallet maybe doesn't work now after the fork, try to start latest official release and put only the wallet.bin.keys file in its folder, wallet bin is not necessary to open the wallet. If that fails you can try Jojatekok GUI wallet but don't sync the complete blockchain, you only need the blockchain portion from the time before the fork in order to be 100% sure its compatible with that old GUI wallet (if you've saved a copy of old blockchain.bin file that would be perfect), then try to enter your password again.
Fingers crossed 

I have a wallet that has been around for a long time and have synced every once in a while.  I received an error when I first ran the bc_height command, but the second time I tried it, it ran and went through all the blocks and that was good to see. But now I have the dust fee problem.

I tried to sweep a small bit of dust from my wallet, it seems that it did not go through, so now there is a 0.02 fee that is stuck in outgoing. Is there a way to remove it or will it go away? I also tried to sweep it again because it showed dust still there, but it errored. Does it even matter?  It's just there in outgoing now for hours.

Also the 0.9.3 doesn't refresh automatically or in the background that I could see, but typing refresh does it. Can it auto refresh? kind of a good thing, like it did before with previous versions it is good to see it sync and then check your balance.