This is actually a regression in Ubiquity 19.04.6 and likely different from the issue observed starting on feb. 4th. 19.04.5 works fine.
This is actually a regression in Ubiquity 19.04.6 and likely different from the issue observed starting on feb. 4th.
19.04.5 works fine.