package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127

Bug #1990588 reported by Sebastian Benvenuti
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Expired
High
Unassigned

Bug Description

updating from server 20.04 to 22.04

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: systemd 249.11-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Sep 22 19:00:53 2022
ErrorMessage: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127
InstallationDate: Installed on 2020-07-28 (786 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Intel IC4GG
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=UUID=8859cc64-d58f-4403-a3dc-284744628c34 ro rootflags=subvol=@ debian-installer/language=es keyboard-configuration/layoutcode?=es consoleblank=60
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, unpackaged
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt 2.0.9
SourcePackage: systemd
Title: package systemd 249.11-0ubuntu3.6 failed to install/upgrade: el subproceso instalado paquete systemd script post-installation devolvió el código de salida de error 127
UpgradeStatus: Upgraded to focal on 2022-09-22 (0 days ago)
dmi.bios.date: 07/03/2012
dmi.bios.release: 0.1
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 63K
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: IC4GG
dmi.board.vendor: Intel
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr63K:bd07/03/2012:br0.1:svnIntel:pnIC4GG:pvr0.1:rvnIntel:rnIC4GG:rvrFAB1:cvnIntelCorporation:ct9:cvr0.1:skuSystemSKUNumber:
dmi.product.family: ChiefRiver System
dmi.product.name: IC4GG
dmi.product.sku: System SKUNumber
dmi.product.version: 0.1
dmi.sys.vendor: Intel
mtime.conffile..etc.systemd.logind.conf: 2020-10-22T18:57:27

Revision history for this message
Sebastian Benvenuti (sebastianbenvenuti) wrote :
Dan Bungert (dbungert)
tags: added: foundations-todo
Changed in systemd (Ubuntu):
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Nick Rosbrook (enr0n) wrote (last edit ):

It seems like for some reason systemd-machine-id-setup was not unpacked correctly? It's trying to link against libsystemd-shared-245.so, which is from focal. It should be linking against libsystemd-shared-249.so instead.

It's called in systemd.postinst, so by that point the new version of the binary should be in place. Does this issue persist? If so, what does `which systemd-machine-id-setup` say? Is it possible you have another version of the binary installed somewhere?

Changed in systemd (Ubuntu):
status: Confirmed → Incomplete
tags: removed: foundations-todo
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for systemd (Ubuntu) because there has been no activity for 60 days.]

Changed in systemd (Ubuntu):
status: Incomplete → Expired
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.