Assuming you are running 1.2.0 or 1.2.1 this has been fixed in 1.2.2 which was released yesterday so an update should fix this. If you are on a version before 1.2.0 it could be something else and it would be handy if you could could complete the template we ask for so we can try and reproduce to get to the bottom of it.