Confirming this behaviour.
It was not the case on a absolutely virgin install of 16.04 (about two weeks ago), but now I have the same problem.
My suspicion is that one of the updates that were published since Xenial's release contains a bug.
Confirming this behaviour.
It was not the case on a absolutely virgin install of 16.04 (about two weeks ago), but now I have the same problem.
My suspicion is that one of the updates that were published since Xenial's release contains a bug.