Comment # 2 on bug 109649 from
I've confirmed that reverting the change on top of 4.20.13 fixes the issue.


You are receiving this mail because: