Comment 25 for bug 498130

Revision history for this message
RarSa (rarsa) wrote :

I used to have EXACTLY the same problem showing exactly the same error message until a few days ago.

It seems to me that the problem is now fixed by one of the updates I've applied since.

Update and confirm if the problem has been fixed for you.