Comment 6 for bug 139593

Revision history for this message
Colin Watson (cjwatson) wrote :

I'm no longer seeing these error messages, so it looks like this has fixed the immediate issue. Thanks.