package xen-utils-common 4.11.3+24-g14b62ab3e5-1ubuntu2.3 failed to install/upgrade: installed xen-utils-common package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xen (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
xen-daemon failed to run
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xen-utils-common 4.11.3+
ProcVersionSign
Uname: Linux 5.15.0-67-generic x86_64
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Wed Mar 22 10:27:58 2023
ErrorMessage: installed xen-utils-common package post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2023-03-21 (0 days ago)
InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3.2
apt 2.0.9
SourcePackage: xen
Title: package xen-utils-common 4.11.3+
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to file a bug report.
On your DpkgHistoryLog.txt file, I see the following:
Start-Date: 2023-03-21 17:45:55
Commandline: apt-get remove xen-upstream
Requested-By: hovan (1000)
Remove: xen-upstream:amd64 (4.17.0)
End-Date: 2023-03-21 17:45:55
We don't ship a xen-upstream package in Ubuntu, which makes me believe that you probably have third-party repositories enabled, or maybe built a Xen package manually. If that's indeed the case, then this is an unsupported scenario where bad interactions between official and non-official Ubuntu packages are likely to happen. In the interest of being thorough, I fired up a VM, installed xen-hypervisor- amd64, removed "xen libxen*", and then tried reinstalling xen-hypervisor- amd64. I could not reproduce the problem you're having.
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://