A past problem has recurred in TrinityX15.2. I tried the solution talked about in #480 but it didn't work. Are there any other possible causes?