failed to install packages from archive despite being online

Bug #2033900 reported by corrado venturini
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
subiquity
Fix Released
Undecided
Unassigned

Bug Description

Installing on nvme disk manual partitioning with English language and Italian keyboard
12th Gen Intel® Core™ i3-12100 × 8

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: subiquity (unknown)
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.482
CurtinAptConfig: /var/log/installer/subiquity-curtin-apt.conf
Date: Fri Sep 1 13:35:54 2023
ExecutablePath: /snap/ubuntu-desktop-installer/1219/bin/subiquity/subiquity/cmd/server.py
InterpreterPath: /snap/ubuntu-desktop-installer/1219/usr/bin/python3.10
LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901)
MachineType: ASUS System Product Name
ProcAttrCurrent: snap.hostname-desktop-installer.subiquity-server (complain)
ProcCmdline: /snap/hostname-desktop-installer/1219/usr/bin/python3.10 -m subiquity.cmd.server --use-os-prober --storage-version=2 --postinst-hooks-dir=/snap/hostname-desktop-installer/1219/etc/subiquity/postinst.d
ProcEnviron:
 LANG=C.UTF-8
 LD_LIBRARY_PATH=<set>
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.4-5
PythonDetails: N/A
SnapChannel:

SnapRevision: 1219
SnapUpdated: False
SnapVersion: 0+git.0117e56d
SourcePackage: subiquity
Title: install failed crashed with CalledProcessError
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2022
dmi.bios.release: 14.2
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1402
dmi.board.asset.tag: Default string
dmi.board.name: PRIME H610M-E D4
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd04/01/2022:br14.2:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610M-ED4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
corrado venturini (corradoventu) wrote :
information type: Private → Public
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2033900

tags: added: iso-testing
Revision history for this message
corrado venturini (corradoventu) wrote :

At end of install I had the bug but new system started fine and i'm writing from the just installed system.
I kept the log and may attach it if needed.

Dan Bungert (dbungert)
summary: - install failed crashed with CalledProcessError
+ failed to install packages from archive despite being online
Changed in subiquity:
status: New → In Progress
tags: added: foundations-todo
Revision history for this message
corrado venturini (corradoventu) wrote (last edit ):

After reboot I can't do update+upgrade, sources.list is broken:
corrado@corrado-n16-mm-0901:~$ sudo apt update && sudo apt upgrade
[sudo] password for corrado:
Get:1 file:/cdrom mantic InRelease
Ign:1 file:/cdrom mantic InRelease
Get:2 file:/cdrom mantic Release
Err:2 file:/cdrom mantic Release
  File not found - /cdrom/dists/mantic/Release (2: No such file or directory)
Hit:3 http://it.archive.ubuntu.com/ubuntu mantic InRelease
Hit:4 http://it.archive.ubuntu.com/ubuntu mantic-updates InRelease
Hit:5 http://it.archive.ubuntu.com/ubuntu mantic-backports InRelease
Hit:6 http://it.archive.ubuntu.com/ubuntu mantic-security InRelease
Reading package lists... Done
E: The repository 'file:/cdrom mantic Release' no longer has a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list
deb [check-date=no] file:///cdrom mantic main restricted
corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/original.list
# Ubuntu sources have moved to /etc/apt/sources.list.d/ubuntu.sources
corrado@corrado-n16-mm-0901:~$ cat /etc/apt/sources.list.d/ubuntu.sources
Types: deb
URIs: http://it.archive.ubuntu.com/ubuntu
Suites: mantic mantic-updates mantic-backports
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Types: deb
URIs: http://it.archive.ubuntu.com/ubuntu
Suites: mantic-security
Components: main restricted universe multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
corrado@corrado-n16-mm-0901:~$ cat /var/log/installer/media-info
corrado@corrado-n16-mm-0901:~$

Will keep this system for future test if needed. Now I'm writing from a Mantic installed in a different partition from the ISO dated 0929.

Revision history for this message
Dan Bungert (dbungert) wrote :

@corrado

So the sources.list file looks wrong but the rest looks fine. This system has been setup with sources in deb822 format (that ubuntu.sources file) - if you move aside the source.list file does it behave correctly?

Dan Bungert (dbungert)
Changed in subiquity:
status: In Progress → Fix Committed
Revision history for this message
corrado venturini (corradoventu) wrote (last edit ):

Yes, after removing sources.list update+upgrade was successful
Thanks

BUT software-properties-gtk seems unable to work with sources in deb822 format

Revision history for this message
Dan Bungert (dbungert) wrote :

Daily builds should be fixed by this point, thanks!

Changed in subiquity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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