Comment 87 for bug 1987976

Gunnar, thanks for reporting on this bug. A quick question: since the original issue got reported in 2022 before kinetic release, what was the status for this in 22.10? Was this also broken there? It's important for us to know if this is a regression or not.

Also, with a visible workaround (re-running firefox), my recommendation would be to release note it, and maybe only include it in case we will need to do a full respin of all desktop RC images for 23.04.