Comment 5 for bug 1452744

Revision history for this message
Miguel Ángel Molina (sslapp) wrote :

This error doesn't appear in 3.13.0-53.60
Changed to fixed!

Thanks