No, this problem existed in earlier kernels also. I've used 16.04 before - and it was the same there. I've also tested it with the latest upstream kernel and it still exists.
No, this problem existed in earlier kernels also. I've used 16.04 before - and it was the same there.
I've also tested it with the latest upstream kernel and it still exists.