Hi @SergeC
I already reported it. It is fixed for the next version, but @shotcut provided instructions to correct it yourself in the current 26.9.27 version if you want.