lubuntu 20.04 debugging `sudo -E calamares -d` requested caused segfault, unable to wipe sda9 fs

[Chris Guiver]

I was requested by wxl/Walter to re-run calamares installer using -d to gain more detail on failures related to
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864787
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864791

Please refer to command #10 & #11 for details on what I did... or in summary
---
Attempt to re-install Lubuntu 20.04 daily over prior Lubuntu 20.04 image.
sda8 is /home for prior install; is being re-used with NO-FORMAT.
sda9 was / and it'll be re-formatted.

I firstly ran QA-test install and got error 1864787. Any notes will be on iso.qa and in on other bug report.

I then exited calamares but did NOT reboot
(*) I opened KDE Partition to ensure no partitions were mounted; I noted that sda9 now showed as UNKNOWN type (as it had before; this bug will now occur). No partitions (inc. swap) were mounted so nothing was done in KDE Partition Manager and I exited

I re-ran the (*) step but this time used `sudo -E calamares -d` where I noted a SegFault.. I hadn't noticed that before (but wasn't usually running calamares from term so maybe it was just me that didn't notice). Nothing unusual appeared on screen.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: calamares 3.2.20-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-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-0ubuntu18
Architecture: amd64
CasperVersion: 1.441
CurrentDesktop: LXQt
Date: Tue Mar 3 15:43:35 2020
ExecutablePath: /usr/bin/calamares
LiveMediaBuild: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200302)
ProcCmdline: calamares -d
RelatedPackageVersions:
 calamares-settings-ubuntu-common 1:20.04.2
 calamares-settings-lubuntu 1:20.04.2
 xfsprogs 5.3.0-1ubuntu1
 btrfs-progs 5.4.1-2
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: calamares
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_source_set_ready_time () from /tmp/apport_sandbox_uct3jxin/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6305.0
 cancellable_source_cancelled (cancellable=<optimized out>, user_data=0x7f049c0950e0) at ../../../gio/gcancellable.c:666
 _g_closure_invoke_va () from /tmp/apport_sandbox_uct3jxin/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6305.0
 g_signal_emit_valist () from /tmp/apport_sandbox_uct3jxin/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6305.0
 g_signal_emit () from /tmp/apport_sandbox_uct3jxin/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.6305.0

[Chris Guiver (guiverc)]

I've had this issue again...
Exploring https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864787 (see comment #13)

dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
testcase: BIOS, internet, no encryption, re-use /home thus manual partitioning

I forgot the `sudo -E calamares -d` to cause calamares to get extra debug info, so re-run
boot 'live' system & use KDE partition manager to erase sda9 (prior / which is listed as unknown after last failed install attempt), apply, then format is ext4 so sda9 again.
deactivate swap then exit KDE partition manager.

open term to use command to run calamares using `sudo -E calamares -d`

Summary - manual partitioning,
- cause format of sda9 (ext4) for '/" &
- no-format for sda8 or /home

Segfaults & ubuntu-bug brought me back here...

[Chris Guiver (guiverc)]

I re-ran command expecting same segfault, alas no issues.

iso.qa.ubuntu detail available at http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/208447/testcases/1701/results

Comment #14 of https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864787 was re-run and where I had crash, then didn't???

I wonder if I loaded and hadn't closed `KDE partition manager` which caused this 'crash'?

I'm tempted to mark this incomplete, and re-try with `kde partition` manager open and see if segfault occurs, as I re-tried the same command expecting failure but didn't have any issues (already mentioned comment #14 of 1864787). I'm tired so operator errors as very possible.

[Chris Guiver (guiverc)]

I loaded `KDE partition manager` and then up-arrow so as to run
sudo -E calamares -d
and it segfaulted.

I exited `KDE partition manager` and ran
sudo -E calamares -d
again, no segfault. I'm marking this incomplete.

[Launchpad Janitor (janitor)]

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