Comment 31 for bug 2051188

Revision history for this message
Paul Rouget (paulrouget) wrote :

@bandali - is it possible the update 123 re-introduced this issue? We're getting reports with the same error.