Comment 3 for bug 280290

Revision history for this message
Nikolaj Sheller (nikolajsheller) wrote :

I may have made a premature conclusion here.
I saw Bug #292139 again.

I think this bug and Bug #292139 are related. Same workaround can be applied.