package python-backports.functools-lru-cache 1.5-3build1 failed to install/upgrade: installed python-backports.functools-lru-cache package post-installation script subprocess returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
backports.functools-lru-cache (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
It just pops up at the Start-Up of my Computer.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python-
ProcVersionSign
Uname: Linux 5.8.0-49-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Fri Apr 9 16:03:49 2021
Dependencies:
ErrorMessage: installed python-
InstallationDate: Installed on 2021-03-18 (29 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
PackageArchitec
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.5, python-is-python2, 2.7.17-4
RelatedPackageV
dpkg 1.19.7ubuntu3
apt 2.0.5
SourcePackage: backports.
Title: package python-
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
Specifically it looks like the Python installation on your system is broken somehow, possibly due to some local intervention.
If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then 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.