Comment 10 for bug 1348070

Revision history for this message
John (publiccomms) wrote :

Upgrading my kernel from 3.19 to 4.3 stopped this error popping up.