A similar issue has been already reported here and a workaround is available, please check if it applies to your setup!