@jsalisbury: just to be clear: it's confirmed that jumping from 4.2.0.27 to the current repo version of linux-image-generic, 4.2.0.34.37, should be safe and avoid this bug?
@jsalisbury: just to be clear: it's confirmed that jumping from 4.2.0.27 to the current repo version of linux-image- generic, 4.2.0.34.37, should be safe and avoid this bug?