lubuntu focal.3 daily - calamares crashed prior install

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

Bug Description

Lubuntu focal.3 (daily) QA-test install on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)

testcase was "install with existing partition"

Box had two installs; focal & impish. impish was re-installed earlier in day, was intending to do the same with focal.

Install selected was NOT "replace partition", but "Manual Partitioning" with intention of selecting sda2 and install without FORMAT, but I didn't get that far.

I was NOT careful (or efficient) with my selections so there was loads of click, look, click look before the crash... I couldn't tell you what I did, but I roughly I
- selected replace partition
- selected sda1, selected sda2 (many times each)
- moved mouse over partitions in order to confirm sda1/sda2 & make balloon show..

(what I consider end-user type behavior, am I correct, is this right..., no click was invalid but they were numerous & equivalent to changing mind, or a user being unsure..)

** actual problem

After playing with "Replace partition" described earlier, I changed to "Manual Partitioning" with intention of selecting SDA2 and calamares closed.

** expected result

Calamares would let me select sda2 at the end of my 'change mind' & let install occur..

** Is this a problem?

I'll repeat install and explore, but this is focal & I can't see any change having occurred.. calamares is just a tad 'fragile' with unsure-users, but so is 'ubiquity`. I'll repeat this type install using 'impish' to explore further. (Next install I won't play; I'll just select sda2 which I knew before I started install anyway)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: calamares 3.2.20-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-56.63~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-56-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-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: LXQt
Date: Thu Jun 17 12:43:06 2021
LiveMediaBuild: Lubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210616)
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:20.04.2
 calamares-settings-lubuntu 1:20.04.2
 xfsprogs 5.3.0-1ubuntu2
 btrfs-progs 5.4.1-2
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Chris Guiver (guiverc) wrote :
Chris Guiver (guiverc)
description: updated
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/1932233

tags: added: iso-testing
Revision history for this message
Chris Guiver (guiverc) wrote :

System was rebooted, live started & install completed on next try.

The difference was lack of selecting this, selecting that, & loads of hovering over partitions to get 'sda1' & 'sda2' to show on map down the bottom.

Either way this report I believe is only valid with the latest release (impish) was used & not OLD FOCAL... but report needed to be done because I encountered issue in QA-test.

Issue is MINOR & annoyance only (for ditherers)

To post a comment you must log in.