Comment 14 for bug 1814393

Revision history for this message
gmaka (gmaka) wrote :

I can confirm that moving back to 4.15.0-43-generic avoids this issue.