Hello Sam,
This is interesting. I was about to point to bug 2017278 but this seems different - because subiquity does an online install.
I was able to reproduce the issue with the latest daily.
Looking at /etc/apt in the target system, I observed that the multiverse component is disabled.
$ grep Components /etc/apt/sources.list.d/ubuntu.sources Components: main restricted universe
which explains why ubuntu-restricted-addons could not be downloaded:
ubuntu-restricted-addons | 29 | mantic/multiverse | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
That said, there was no disabled_components set in /var/log/installer/subiquity-curtin-apt.conf.
This could indicate a bug in the deb822 sources handling by curtin.
That said, deb822 sources in curtin should be disabled (it was pushed back because of a bug in software-properties).
I think the ubuntu-budgie-installer needs to update to a more recent version of ubuntu-desktop-provision.
Hello Sam,
This is interesting. I was about to point to bug 2017278 but this seems different - because subiquity does an online install.
I was able to reproduce the issue with the latest daily.
Looking at /etc/apt in the target system, I observed that the multiverse component is disabled.
$ grep Components /etc/apt/ sources. list.d/ ubuntu. sources
Components: main restricted universe
which explains why ubuntu- restricted- addons could not be downloaded:
ubuntu- restricted- addons | 29 | mantic/multiverse | source, amd64, arm64, armhf, ppc64el, riscv64, s390x
That said, there was no disabled_components set in /var/log/ installer/ subiquity- curtin- apt.conf.
This could indicate a bug in the deb822 sources handling by curtin.
That said, deb822 sources in curtin should be disabled (it was pushed back because of a bug in software- properties) .
I think the ubuntu- budgie- installer needs to update to a more recent version of ubuntu- desktop- provision.