Calamares fails -External command finished with errors

[Leó Kolbeinsson]

Calamares fails -External command finished with errors

Testing Lubuntu Noble daily ISO dated 06-11-2023 machine running in UEFI+secure boot mode

see attached screenshot

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.0-alpha4-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
.etc.calamares.modules.after_bootloader_context.conf:
 ---
 dontChroot: false
 timeout: 120
 firmwareType:
     "*": "-rm ${ROOT}/home/${USER}/Desktop/lubuntu-calamares.desktop"
.etc.calamares.modules.finished.conf:
 ---
 restartNowMode: user-checked
 restartNowCommand: "systemctl -i reboot"
.etc.calamares.modules.fstab.conf:
 crypttabOptions: luks,keyscript=/bin/cat
 efiMountOptions: umask=0077
.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.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.486
CurrentDesktop: LXQt
Date: Tue Nov 7 08:16:58 2023
LiveMediaBuild: Lubuntu 24.04 "Noble Numbat" - Daily amd64 (20231106)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:23.10.4
 calamares-settings-lubuntu 1:23.10.4
 xfsprogs 6.3.0-1ubuntu1
 btrfs-progs 6.3.2-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:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2042911

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[sudodus (nio-wiklund)]

Tried to install alongside Windows 11 in a Lenovo V130 with Intel i5 7200U replacing an old Focal system (reusing its partition). Running in UEFI mode with secure boot.

Externt kommando kördes färdigt med fel <--> External command finished with error

See the attached screenshot.

[sudodus (nio-wiklund)]

While reporting (the failure in my previous comment) a new version (dated Nov 7) was uploaded. I zsynced and cloned it to my SSD, and the same failure occurred (described in my previous comment and its attached screenshot).

[Leó Kolbeinsson (leok)]

2 tests run on daily ISO dated 07-11-2023 Lubuntu Noble
one on barebone machine running in UEFI śecure boot mode which failed
and the second on in BIOS mode in a VirtulaBox VM which was without error.

[sudodus (nio-wiklund)]

I had saved a working iso file dated 2023-11-02 (with clocktime 16.59.29.00 according to its UUID as seen by lsblk -fm). I tested it again, and yes it can still create a working installed system alongside Windows in UEFI mode with secure boot.

So which packages in the iso file were updated after that date and time; what caused this bug?

[sudodus (nio-wiklund)]

Same use case as yesterday and day before yesterday, still 'external command error', but new text in the error message window with the iso file dated Nov 8. See the attached screenshot.

[sudodus (nio-wiklund)]

Installation alongside Windows in a Lenovo V130 in UEFI mode with secure boot works with the current iso file (dated Nov 10 but tested Nov 11), and the installed system works (at once and after upgrade and reboot) :-)

[Simon Quigley (tsimonq2)]

Is this still an issue?

[Launchpad Janitor (janitor)]

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

[Leó Kolbeinsson (leok)]

Marked as new - as this issue is still present Lubuntu Noble daily ISO dated 14-03-2024

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

A screenshot and a log would be helpful since there are multiple different things that have been mentioned on this bug. What's the minimum requirements? Alongside with UEFI and secure boot?

[Leó Kolbeinsson (leok)]

Sorry for the confusion -- I should not have marked this as new ..should have filed a new bug and will do after re-test.

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

FWIW I just did an install alongside with UEFI and secure boot. Admittedly the first OS was another Lubuntu and not Windows, but still, it's not clear what conditions are necessary to reproduce this nor what the exact symptoms are.