Hi,

Is this bug fixed in v6.60?