Bitcoin-Balance doubles but can't be send

[GoogleCodeExporter]

What steps will reproduce the problem?
1. The following transactions "took place" in my bitcoin-wallet:

+0.05
+0.5
+4.8906
-5
+0.001

( http://blockexplorer.com/address/1Fk7jQFinMYofLPKnLr5TFfAHMDhqTQg4P )

2. The wallet-app shows as balance BTC 0.6822, which is wrong (should be BTC 
0.3416).

3. On the sending-screen I get the notification "BTC 0.6822 warten auf 
Bestätigung" (BTC 0.6822 waiting for verification) and can't send any bitcoins.

What is the expected output? What do you see instead?

The balance should be BTC 0.3416 .

What version of Bitcoin Wallet are you using? On what Android version and
what phone? Don't just state 'most recent', this is not enough info.

The app is version 1.39 . My phone (a Motorola Milestone) runs Android 2.2.1 .

If you have problems with particular transactions, what is your Bitcoin
address? If you happen to have transaction IDs, please state them as well.

http://blockexplorer.com/address/1Fk7jQFinMYofLPKnLr5TFfAHMDhqTQg4P

Please provide any additional information below.

Obviously the problem results from the -5 BTC booking. Without the additional 
0.001 BTC the balance in my wallet was exactly twice as high as it should have 
been (BTC 0.6812 instead of BTC 0.3406).
Whenever I restart the wallet-app that transaction is put on top of the  list 
and marked with the time of the app-start.

Original issue reported on code.google.com by m...@davidp.de on 6 Nov 2011 at 9:10

[GoogleCodeExporter]

P.S. I've already tried to reset the blockchain and transaction-list (yes, I've 
read the "Use only when being instructed.", but I was curious ;) ), this 
doesn't change anything.

Original comment by m...@davidp.de on 6 Nov 2011 at 9:19

[GoogleCodeExporter]

now it's gone totally wild. new balance showing up is BTC 6.3634 .

Original comment by m...@davidp.de on 6 Nov 2011 at 9:58

[GoogleCodeExporter]

after resetting blockchain and transactions again, now the balance is correct.

anyway: would be interesting to know, how this could have happend and ho to 
avoid this in the future.

Original comment by m...@davidp.de on 6 Nov 2011 at 3:47

[GoogleCodeExporter]

Probably a leftover from version 1.36, which had a nasty bug. I'll close this 
for now, thanks for reporting.

Original comment by andreas....@gmail.com on 25 Nov 2011 at 8:09

• Changed state: Fixed