I remember that someone mentioned a similar problem before. I saw that the update log seemed to be fixed, but after I upgraded to the latest version, the problem as shown in the figure still appeared.