I just got this with 16.04 and virtualbox 5.1.2
So whose bug is this exactly? It results in a poor installation experience in virtualbox, unfortunately. Never run into it before now.
I just got this with 16.04 and virtualbox 5.1.2
So whose bug is this exactly? It results in a poor installation experience in virtualbox, unfortunately. Never run into it before now.