Comment 2 for bug 659876

As a guess, the client uses the "State" indicator to tell if it can start a sync or not. And since the state was incorrect, it allowed me to launch a new one. I did check again, and I couldn't start a 3rd Sync.

I wonder if it is because the client crashed and I restarted it. And it didn't determine that it was already Synching. Maybe it needs a way to poll-on-startup the current state?