Comment # 3 on bug 1045723 from Franck Bui

This was finally been fixed by upstream, see commit
088696fe29e1eadeced40a5a2b277570f0955164, which will be part of v239 when it
will be released.

That said as this commit depends on other changes, I don't think it is worth
backporting the whole set of changes because there would be a risk of
introducing regressions and since you have already used a workaround since
almost 1 year I think it's safer to wait a bit more until v239 is out to get
this one fixed.

So I'll close this one as UPSTREAM.

Hope that makes sense.