Looks like the bug got attention in the other forum thread:
This problem is expected to be fixed in 25.10.1.