Hmm, there was a report of a similar sounding issue here:
But it was supposedly resolved with the release of (I think) the version you are running:
To try to distinguish whether this is a problem with your setup or a lingering 1.2 bug, you could try installing the current regular stable release (1.1.456).