Hey just wanted to get back to you once again, and announce that the problem should be solved with the new 1.4.1 hot-fix update.