lubuntu calamares (noble) lets users make poor decisions

Bug #2048727 reported by Chris Guiver
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calamares (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm a user, and users can be ....

Boot current daily; selected install (after changing language to AU) & calamares starts.
The lubuntu-installer-prompt dialog did NOT allow me to select my wifi, so I just ignored it.

- sony vaio ultrabook svp11216cgb (i5-9400u, 4gb, intel haswell-ULT)

I selected XFS file-system, accepted swap & full installation.

I was offered options such as additional additional packages & additional stuff (despite not having internet).. I opted for the extras

** actual outcome

Install failed (so I was told; I've not rebooted so can't confirm that yet, but calamares reported it as having failed & started live session where I'm filing this..)

** expected outcome (alternatives)

Due to my not having internet; maybe one of the following

- I should maybe NOT have been able to select to install packages that are NOT on the ISO/install media maybe

- A warning telling me to expect problem since my selected options weren't possible without internet. The much earlier (no internet) screen easily forgotten (by us users especially; we're idiots). AT minimum this should be documented in release notes (something to point to in support)

(this needs a duplicate check; i doubt this will be the first reporting of this, I've mentioned it before on irc anyway)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: calamares 3.3.0.0-0ubuntu5
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-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-0ubuntu6
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.490
CurrentDesktop: LXQt
Date: Tue Jan 9 15:15:24 2024
LiveMediaBuild: Lubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240108.1)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:24.04.11
 calamares-settings-lubuntu 1:24.04.11
 xfsprogs 6.5.0-1ubuntu2
 btrfs-progs 6.6.3-1
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
description: updated
Revision history for this message
Chris Guiver (guiverc) wrote :

I passed the install, as on reboot the system booted; and I was able to login

NO /var/log/installer/ directory existed to confirm ISO date etc...

but file-system metadata (contents & / directory date/times etc) all looks good matching new install. calamares just stopped on error thus didn't complete.

Revision history for this message
Chris Guiver (guiverc) wrote :

I didn't find duplicate of this (which doesn't mean there isn't one)

calamares is running when the end user (smart or stupid) decides what options they'll use.. which may or may not have internet available; with warning shown early in the process if internet isn't available (easily forgotten by us dumb users).

another option that maybe somewhat easy for us to implement is a warning in lubuntu-installer-prompt IF internet isn't detected. ie. checking for internet & display warning at bottom if not connected...

If user uses lubuntu-installer-prompt to connect to wifi, then that app restarts (as I understand it) which would (I'd expect) mean the warning about (you can't opt to download/install extra apps) would be removed..

a thought anyway (if this makes sense)

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:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2048727

tags: added: iso-testing
To post a comment you must log in.