This is still happening after a fresh install of 0.3.1 (originally the bug was filed while running 0.3.0)
This is still happening after a fresh install of 0.3.1 (originally the bug was filed while running 0.3.0)