Another user reported this in @ChuckPa 's Linux packaging thread; it looks like the problem has been identified and corrected: