Yes, we experienced it with 1.4.1.4 in the last couple of weeks, it has been a long-standing bug and is still happening as far as I know.
Are you sure you followed step 5 and were starting on a site with no other elements of that type already present - that is the crucial part - this bug only happens when there are no elements already existing.
I did follow all the steps detailed in your post but did not run into this error. I will repeat again (with screencast) and see if I run into the issue.