lubuntu groovy install failed; message is larger than screen allows for

[Chris Guiver]

Lubuntu groovy daily install on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
testcase: full disk, encryption, uEFI, internet

this bug is likely just bad-luck (timing), however the message contains loads of detail, too much for what the screen can handle (see screen.jpg), which doesn't help & maybe scary for non-technical users.

key bits I see in messages are
- "File has unexpected size"
- "Hashes of expected file"
- "Mirror sync in progress?"
so result of bad luck???

Final message from `calamares` was failed install.

On reboot, the system booted normally & on quick exploration I didn't find any faults (I upgraded packages manually).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: calamares 3.2.24-0ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.partition.conf:
 efiSystemPartition: "/boot/efi"
 enableLuksAutomatedPartitioning: true
 userSwapChoices: none
 drawNestedPartitions: true
 defaultFileSystemType: "ext4"
.etc.calamares.modules.shellprocess_logs.conf:
 ---
 dontChroot: true
 timeout: 30
 script:
     - calamares-logs-helper @@ROOT@@
.etc.calamares.modules.unpackfs.conf:
 ---
 unpack:
     - source: "/cdrom/casper/filesystem.squashfs"
         sourcefs: "squashfs"
         destination: ""
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: LXQt
Date: Tue Oct 20 12:31:00 2020
LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201019)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:20.10.11
 calamares-settings-lubuntu 1:20.10.11
 xfsprogs 5.6.0-1ubuntu4
 btrfs-progs 5.7-1
SourcePackage: calamares
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/1900637

[ԜаӀtеr Ⅼарсһуnѕkі (wxl)]

Since it doesn't seem like this is reproducible, my guess is it was a matter of what is ultimately a temporary issue. A mirror sync would be syncing the archive mirror (in Australia in your case) to the canonical/Canonical ☺ mirror. If getting all the index files happened before the sync, but a package that had changed during the sync was being downloaded after the sync, then we'd have this problem. Repeating the process almost immediately should yield positive results.

[Launchpad Janitor (janitor)]

[Expired for calamares (Ubuntu) because there has been no activity for 60 days.]