@Jon I think this bug was resolved few days ago when 4.3.11 was released in both Xenial and Trusty updates.
@Jon I think this bug was resolved few days ago when 4.3.11 was released in both Xenial and Trusty updates.