This bug seems to be fixed (at least on my machine) in the HEAD revision from git repo as well as source available at sourceforge.net (0.6.4).
This bug seems to be fixed (at least on my machine) in the HEAD revision from git repo as well as source available at sourceforge.net (0.6.4).