install failed crashed with ClientError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
I tried to install Ubuntu 23.10 with TPM FDE in a virtual machine with virt-manager (using /usr/share/
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSign
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckR
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/
CurtinAptConfig: /var/log/
Date: Tue Apr 30 14:23:13 2024
DesktopInstalle
ExecutablePath: /snap/ubuntu-
InterpreterPath: /snap/ubuntu-
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcAttrCurrent: snap.hostname-
ProcCmdline: /snap/hostname-
ProcEnviron:
LANG=de_DE.UTF-8
LD_LIBRARY_
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/
PythonDetails: N/A
SnapChannel: latest/stable
SnapRevision: 1286
SnapUpdated: False
SnapVersion: 0+git.0057491b
SourcePackage: subiquity
Title: install failed crashed with ClientError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/11/2024
dmi.bios.release: 0.0
dmi.bios.vendor: Ubuntu distribution of EDK II
dmi.bios.version: 2024.02-2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnUbuntudi
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.
dmi.sys.vendor: QEMU
Changed in subiquity: | |
status: | Incomplete → New |
Hi Ben, thanks for the report.
Snapd has reported the following about the machine:
Finish setup of run system for "enhanced- secureboot- desktop" (cannot seal the encryption keys: cannot add EFI secure boot policy profile: cannot compute secure boot policy profile: the current boot was preceeded by a boot attempt to an EFI application that returned to the boot manager, without a reboot in between)
I'm not entirely sure what you do about that - is a reboot really enough? - but that's what's going on and why it failed.