Sending a transaction before the client fully synchronises makes it not transmit

[ThePiachu]

I am running the client version 0.8 and wanted to do a quick transfer. Loaded up the client, then as soon as the main window came up I filled out the transaction details and clicked send. The client then proceeded to connect to the peers, synchronise everything, and when it was done, the transaction still had 0 confirmations and was not transmitted to any peer. Waited for a minute, restarted the client, still nothing. I issued an identical transaction again, that one sent (and confirmed), while I still can see the old transaction sitting in my client doing nothing.

[qubez]

1. Is it possible that some of the inputs of the first transaction are already spent?
2. After leaving Bitcoin up and connected for several hours, long enough that pending transactions would be retransmitted, does the transaction appear on the unconfirmed list at http://bitcoincharts.com/bitcoin/txlist/
3. Did the recreated payment use different coin inputs? If so, you probably want to immediately remove the unconfirmed transaction from your wallet using pywallet so the recipient isn't paid twice.

I always wait for some connections before issuing a transaction, as it makes sense to have some relay nodes to send the transaction to. Some testing would be required to see if this can be replicated, and determine if it is related to having no connections and the tx not being immediately advertised to new connections (this appears to be the case based on ThePiachu's reply), or is due to issues with the unsynchronized blockchain and uninformed input selection because of this.

[ThePiachu]

The transaction did confirm in the end, so it was not a double-spend. This wasn't until I started the client up again later.

[rebroad]

@ThePiachu Do you mean that both transactions eventually got confirmed? If so, why is this issue still open?