Kubuntu OEM Installer crash when clicking next
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
- Install Kubuntu 21.10 as OEM installation
- First boot into installer, follow until account creation
- enter account details, click next
- clicking "next" on the next screen crashes the installer
Error message:
Installer Crashed
Traceback (most recent call last):
File "/usr/lib/
ui=self.
IndexError: list index out of range
This happens both in VMs as well as on 2 different Intel machines.
Unfortunately I can't attach any other logs, as there is no possibility to open a terminal.
Also "oem" user account password is unknown and a login via tty is therefore impossible
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckR
CasperVersion: 1.465
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.10
InstallCmdLine: BOOT_IMAGE=
LiveMediaBuild: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
Package: ubiquity 21.10.10
PackageArchitec
ProcVersionSign
Tags: impish ubiquity-21.10.10 kubuntu
Uname: Linux 5.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
Changed in ubiquity (Ubuntu): | |
status: | Incomplete → New |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1955542
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.
If you cannot run this from the installed system, please boot the installation media on the machine you installed on and run `apport-collect` from there (that will provide release details as well as the relevant hardware details). Please leave a comment if you do this, so it's known how the details provided relate to your issue. Currently no release details are known, nor what ISO was used to install, etc. so it's difficult to evaluate the issue.
After running `apport-collect` the status can be returned to "New". If you're unable to complete this; please leave a comment with details (and the status can also be returned to "New").