Comment 2 for bug 1972683

Revision history for this message
Tony Middleton (ximera) wrote :

This seems to be a duplicate of 1242417. However the fix applied for that bug didn't fix the underlying problem but instead created a workaround that was sufficient for the case that led to the bug. It does not fix the situation reported here.