Kubuntu Jammy Jellyfish daily-live test install crashes

Bug #1950132 reported by Bob H
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

making a test installation of latest daily jammy jellyfish [kubuntu 2204]
install to a thumb drive successful
begin install to PC using manual partitioning
nVidia machine so using safe graphics

install crashed just before completion
previous daily (2021-11-07) installed without error

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 21.10.10
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: KDE
Date: Mon Nov 8 08:13:06 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211108)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Bob H (bobbicat) wrote :
Bob H (bobbicat)
summary: - jammy jellyfish alpha test install crash
+ jammy jellyfish daily test install crash
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote : Re: jammy jellyfish daily test install crash

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/1950132

tags: added: iso-testing
Bob H (bobbicat)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Bob H (bobbicat) wrote (last edit ):

This bug has now appeared in several consecutive daily releases of kubuntu2204
reports made on each occasion
crashed and failed Monday 08 November 2021
crashed and failed Tuesday 09 November 2021
before these dates daily installations passed

jammy jellyfish kubuntu daily cannot be installed

Revision history for this message
Leó Kolbeinsson (leok) wrote :

This also affects Xubuntu ISO 10-11-2021 crased and failed.

http://iso.qa.ubuntu.com/qatracker/milestones/429/builds/239484/testcases/1300/results

Revision history for this message
Tobias Karnat (tobiaskarnat) wrote :

This also affects MATE ISO 10-11-2021 crashed and failed.

https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950504

Revision history for this message
Leó Kolbeinsson (leok) wrote :

This also affects Ubuntu Jammy ISO 11-11-2021

Norbert (nrbrtx)
summary: - jammy jellyfish daily test install crash
+ Kubuntu jammy jellyfish daily test install crash
Revision history for this message
Bob H (bobbicat) wrote (last edit ): Re: Kubuntu jammy jellyfish daily test install crash

On 2021-11-07 daily-live Kubuntu Jammy Jellyfish INSTALLED without error.

On 2021-11-08 a change had occurred which created bug 1950132.
This change prevents/stops installation at the slideshow stage.

I'm not a programmer or developer but I humbly suggest that a comparison of the changes from the 2021-11-07 version to the 2012-11-08 version might show where the problem lies.

I think this is true for other flavours including Ubuntu itself.

I would do such a comparison myself and deal with it if I knew how but my expertise is very limited..

summary: - Kubuntu jammy jellyfish daily test install crash
+ Jammy Jellyfish daily test install crash
summary: - Jammy Jellyfish daily test install crash
+ Jammy Jellyfish daily-live test install crash
summary: - Jammy Jellyfish daily-live test install crash
+ Jammy Jellyfish daily-live test install crashes
Bob H (bobbicat)
description: updated
Revision history for this message
pqwoerituytrueiwoq (pqwoerituytrueiwoq) wrote : Re: Jammy Jellyfish daily-live test install crashes

when it crashed for me twice it was as soon as it tried to use apt, maybe something changed with apt and broke the installer?

Screenshot from where i found the issue https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950880/+attachment/5540733/+files/Screenshot_20211113_214834.png

Norbert (nrbrtx)
summary: - Jammy Jellyfish daily-live test install crashes
+ Kubuntu Jammy Jellyfish daily-live test install crashes
Revision history for this message
Bob H (bobbicat) wrote (last edit ):

@ pqwoerituytrueiwoq

your screen shot shows what happens with this bug
it is what occurred during my attempted install

did you follow through and file a bug report?

I couldn't begin to guess what the problem is

I only know I encounntered it on 2021-11-08
tests before that had completed successfully

I hope someone with the expertise to deal with this comes along

Revision history for this message
Norbert (nrbrtx) wrote :

The same "plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 127"

is the reason of the crash.

Revision history for this message
pqwoerituytrueiwoq (pqwoerituytrueiwoq) wrote :

@Bob H (bobbicat)
https://bugs.launchpad.net/bugs/1950880

the bug id was in the screenshot url

Revision history for this message
oldfred (oldfred) wrote :

Do not know login password when using installer. Its in an encrypted file in my main working install.

Error posted:

kubuntu@kubuntu:~$ ubuntu-bug ubiquity
/usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python.
  progress.setValue(value * 1000)
/usr/bin/which: this version of `which' is deprecated; use `command -v' in scripts instead.

Latest ISO from Nov. 21.
Booted using grub2's loopmount.
Have to umount /isodevice or it crashes (all older versions were same).
Used manual partitioning to reuse existing old install, changed (tried to) ESP from sda1 to sdb1, but had to umount /sda1 and mount sdb1 as ESP while on screen adding login info.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.