This is fixed for the 6.7 release in rev#83784. The fix won't be apply to 6.6 and the suggested workaround is what to do in the meantime.