The fix for bug 1205285, which went into the 20130716.1 image indeed seems to have fixed this for us. Duping to that one Thanks Oliver!
The fix for bug 1205285, which went into the 20130716.1 image indeed seems to have fixed this for us. Duping to that one
Thanks Oliver!