I'm not sure whether this is a ubiquity bug because it has not been proven that it was ubiquity that put it there. If you assume that the name change and the default install are both the same bug, then it can't be ubiquity that caused this bug
I'm not sure whether this is a ubiquity bug because it has not been proven that it was ubiquity that put it there. If you assume that the name change and the default install are both the same bug, then it can't be ubiquity that caused this bug