Unchecking all optional media apps, install fails

[MarkF]

ISO testing 20.04 Studio's daily image (20200319). A screen appears with about a dozen various media/photography apps which are checkmarked. I am invited to uncheck any or all. I unchecked all. The install fails near the end. There is an "oopsie" msg which disappears, and the installation ends. When I reboot, I'm dropped at a command-line login.

I saw this with yesterday's daily image too. But, I haven't tried this before. It could have always been this way.

FWIW: unchecking all those media apps results in the installation taking 3-4 times longer. I expected it to install very fast. It never does complete. The progress bar is about 4/5ths of the way to the right edge, and then the oopsie msg occurs. I Ubuiquity disappears after that. It seems to be removing packages for a long time when this happens.

Maybe nobody would ever uncheck all. It's probably not an important problem. I just wanted to bring it to someone's attention.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.6
ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24
Uname: Linux 5.4.0-18-lowlatency x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
CasperVersion: 1.441
CurrentDesktop: XFCE
Date: Fri Mar 20 01:23:11 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed quiet splash ---
LiveMediaBuild: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200319)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

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

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

[Erich Eickmeyer (eeickmeyer)]

Might be related to bug 1851346.

[MarkF (az2008)]

IMPORTANT: this bug-report DIFFERS FROM #1851346 in one important way: The INSTALLER FAILS, not merely goes slow.

ALSO, it DOESN'T MERELY FAIL. It (essentially) FAILS WITHOUT NOTICE (unless the user is watching the the entire (and now-slow installation). If they return from doing something else, everything will look fine (to the uninitiated). When they reboot, they will be presented with a COMMAND-LINE LOGIN PROMPT without any context about why that might be.

Personally, I would not call this a duplicate. But, the other bug report has been duly updated to keep this info alive.