On 05/04/17 15:28, Florian Lohoff wrote: > although 5.3.1 is unaffected by the bug - this machine still is due > to incomplete upgrade. Ah-ha! Problem solved - read the upgrade guides carefully. :) And do upgrade to at least 5.3.4 whilst you're at it. -- Tom