Comment 12 for bug 1605948

Revision history for this message
Jun Yamut (jun-yamut) wrote :

Getting this exact same error after updating today. The workaround suggested above does not fix this issue. I'm on 16.04.3.