On Thu, 2026-09-17 at 19:42 +0100, Simon McVittie wrote:
> This is likely to be fixed in 51.0-2

Thanks, I can confirm updating from 51.0-1 to 51.0-3 fixed the issue
I'd reported in 1148156.

Antoine

Reply via email to