Comment 76 for bug 1492764

Revision history for this message
Ljiljan Veselinovic (ljiljan-veselinovic) wrote :

I was surprised that with 4.2.0-23-generic update, this error is gone... I hope forever :-)