package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1

[Guillaume]

This happened as I was upgrading my system from 16.04 to 18.04 (no problem on that part) and then to 20.04 (where the problem happened.

ProblemType: Package
DistroRelease: Ubuntu 20.04
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jan 28 12:02:11 2021
ErrorMessage: new lxd package pre-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2016-08-14 (1627 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt 2.0.4
Snap: lxd 4.0.4 (4.0/stable)
Title: package lxd (not installed) failed to install/upgrade: new lxd package pre-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2021-01-28 (0 days ago)

[Chris Guiver (guiverc)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

[Guillaume (xiu42)]

No worries, I reported this bug as the installer told me to. After restarting the upgrade, the problem want away and I was able to finish.

Feel free to close this one if it doesn't qualify as a bug.

Thanks!

[Paul White (paulw2u)]

Further to comment #3, belatedly closing this issue as reporter says "the problem want away and I was able to finish." Nothing to investigate so not now really a valid bug report.