I am unable to reproduce this error further.
This happened twice on separate VMs when upgrading to 16.04 from clean installs of 14.04.4.
It has stopped happening on further upgrade attempts, so I would tend to think that it has been fixed, maybe as a side effect of some other update?
I am unable to reproduce this error further.
This happened twice on separate VMs when upgrading to 16.04 from clean installs of 14.04.4.
It has stopped happening on further upgrade attempts, so I would tend to think that it has been fixed, maybe as a side effect of some other update?