I have the same and found bug #600578 with an explanation about this. #600578 should probably re-opened since the solution for one scenario breaks it at other scenarios. Regards -- hgb