Comment 48 for bug 1542733

Revision history for this message
Christopher (cwkeller) wrote :

Under 16.04.01 still no further error as of 15. May 2017, so I assume updates have resolved the problem.
Christopher