Now i tried the last nightly build of 2.1.0 but the problem still exists. I think we need to open a ticket about this error?That should not come as a surprise. "someone" is well known not to be very (pro)active when it comes to fixing bugs. Patch welcome.