Budgie Installer fails with internet enabled / additional media support selected

Bug #2036966 reported by Sam Lane
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
subiquity
Invalid
Undecided
Unassigned
livecd-rootfs (Ubuntu)
Fix Released
Undecided
Dan Bungert

Bug Description

When installing Ubuntu-Budgie 23.10 "Mantic Minotaur" - Daily amd64 (20230920)
With internet enabled and selecting the option to "Downloand and install support for additional media formats", the installer produces a crash, and a Failed to Install message.

Steps to reproduce:
- Starting from the daily Budgie Mantic Minotaur amd64 (20230920) iso, boot the iso
- connect to a wifi network
- run the installer
- during the install, at the Applications & Updates menu:
  - Select Ubuntu Budgie Desktop (full install option)
  - check "Download and install support for additional media formats"
- selected Erase disk and Install Ubuntu Budgie
- run through rest of install options

The installer results in a Failed to Install message. When looking at the output in the installer, I can see a message:
system install failed for ['ubuntu-restricted-addons']: Unexpected error when running the command

I have attached the .crash file as well as the tarball for /var/log/installer

Tags: iso-testing

Related branches

Revision history for this message
Sam Lane (samlane00) wrote :
Revision history for this message
Sam Lane (samlane00) wrote :
Revision history for this message
Olivier Gayot (ogayot) wrote :

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.

Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2036966

tags: added: iso-testing
Revision history for this message
Sam Lane (samlane00) wrote :

I have given this another go with the newest edge version of the ubuntu-budgie-installer snap. Booted with the Ubuntu Budgie beta iso (20230920).

Opened a terminal and performed a snap refresh:
ubuntu-budgie@ubuntu-budgie:~$ snap refresh ubuntu-budgie-installer --channel edge
ubuntu-budgie-installer (edge) 0+git.a38f4ea from Ubuntu budgie (ubuntubudgie) refreshed

Double-checked version with: snap list
ubuntu-budgie-installer 0+git.a38f4ea 28 latest/edge ubuntubudgie classic

Repeated the same steps, checking the box for installing the support for additional media formats.

I ran into the same installation failed message as before, with the message:
system install failed for ['ubuntu-restricted-addons']: Unexpected error when running the command

Attached are the new logs / .crash file

Revision history for this message
Sam Lane (samlane00) wrote :
Revision history for this message
Dan Bungert (dbungert) wrote :

I agree with Olivier. Relevant work was done very recently, and I believe did not make the beta for Budgie. This should be retested after daily builds start again and after the newer ubuntu-desktop-provision is used. Thanks.

Revision history for this message
Olivier Gayot (ogayot) wrote :

I tested it again after snap refresh as you did Sam. Multiverse still ends up disabled on the target system.

Looking into /cdrom/casper/minimal.squashfs, multiverse is disabled there as well, so I assume it is an intended configuration on Budgie ? It likely rules out a deb822 sources bug.

With the old installer though (i.e., 22.04.3), multiverse ends up being enabled on the target system despite not being present in /cdrom/casper/filesystem.squashfs.

Is there any reason not to build the budgie ISO with multiverse enabled ? I assume rebuilding with multiverse enabled would be the simplest approach.

Revision history for this message
fossfreedom (fossfreedom) wrote :

Olivier - no reason that multiverse isn't enabled as far as I know. To be honest I thought it always was enabled. I presume this is a release team ask to update? I've pinged on IRC #ubuntu-release today.

Revision history for this message
Olivier Gayot (ogayot) wrote :

@fossfreedom Thanks for checking! Then I guess it's the right solution going forward. And #ubuntu-release feels like the best place to ask.

Best regards,
Olivier

Revision history for this message
Olivier Gayot (ogayot) wrote :

Adding livecd-rootfs. The live installer environment is configured with multiverse enabled but /cdrom/casper/minimal.squashfs does not - so we end up:

 * failing to install ubuntu-restricted-addons
 * leaving the target system without multiverse

$ unsquashfs -dest /tmp/test /cdrom/casper/minimal.squashfs etc/apt
$ cat /tmp/test/etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu/ mantic main restricted universe
deb http://security.ubuntu.com/ubuntu/ mantic-security main restricted universe
deb http://archive.ubuntu.com/ubuntu/ mantic-updates main restricted universe

Dan Bungert (dbungert)
Changed in livecd-rootfs (Ubuntu):
status: New → In Progress
assignee: nobody → Dan Bungert (dbungert)
Revision history for this message
Dan Bungert (dbungert) wrote :

When livecd-rootfs 23.10.45 migrates, the sources.list should look like the normal template instead of the 3-line one that had no multiverse.

Changed in livecd-rootfs (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Dan Bungert (dbungert) wrote :
Changed in subiquity:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package livecd-rootfs - 23.10.45

---------------
livecd-rootfs (23.10.45) mantic; urgency=medium

  * budgie: Configure universe & multiverse sources (LP: #2036966)

 -- Dan Bungert <email address hidden> Mon, 25 Sep 2023 13:57:21 -0600

Changed in livecd-rootfs (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.