package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python3-defaults (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
It fucked up my dsektop. It went total blank.
I manage to fix my desktop by removing everything in the etc/Python2.7/ file, since it hindered me from using apt-get -f install and installing my packages for different programs. And also from reinstalling ubuntu-desktop.
Once i removed it i could reinstall the ubuntu-desktop and the OS works again.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3 3.5.1-3
ProcVersionSign
Uname: Linux 4.4.0-66-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 22 15:02:20 2017
DuplicateSignature:
package:
Removing python3 (3.5.1-3) ...
/var/lib/
dpkg: error processing package python3 (--purge):
subprocess installed pre-removal script returned error exit status 127
ErrorMessage: subprocess installed pre-removal script returned error exit status 127
InstallationDate: Installed on 2017-02-08 (44 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: python3-defaults
Title: package python3 3.5.1-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)
| Oskar Friberg (freeberg) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| tags: | removed: need-duplicate-check |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1671837, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.