install failed crashed with CalledProcessError
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
I was interrupted between typing password and repeating the password (for login). Maybe it is a duplicate of a recent bug report.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: subiquity (unknown)
ProcVersionSign
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelMo
ApportVersion: 2.27.0-0ubuntu6
Architecture: amd64
CasperMD5CheckR
CasperVersion: 1.487
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/
CurtinAptConfig: /var/log/
Date: Fri Nov 17 18:33:14 2023
DesktopInstalle
ExecutablePath: /snap/ubuntu-
InterpreterPath: /snap/ubuntu-
LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231117)
MachineType: TOSHIBA SATELLITE PRO C850-19W
ProcAttrCurrent: snap.hostname-
ProcCmdline: /snap/hostname-
ProcEnviron:
LANG=C.UTF-8
LD_LIBRARY_
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Python3Details: /usr/bin/
PythonDetails: N/A
SnapChannel:
SnapRevision: 1272
SnapUpdated: False
SnapVersion: 0+git.417b2d8a
SourcePackage: subiquity
Title: install failed crashed with CalledProcessError
UdiLog: Error: [Errno 40] Too many levels of symbolic links: '/var/log/
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/24/2012
dmi.bios.release: 6.10
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 6.10
dmi.board.
dmi.board.name: PLCSF8
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.family: Type1Family
dmi.product.name: SATELLITE PRO C850-19W
dmi.product.sku: PSCBXE
dmi.product.
dmi.sys.vendor: TOSHIBA
Tried to install with encryption, maybe the same bug as reported previously,
https:/ /bugs.launchpad .net/subiquity/ +bug/2043585
but I am not sure about the symptoms, so I report as a separate bug.
I tried again (so twice with today's daily build) and the same thing happened.