package libapr1:amd64 1.5.1-3 failed to install/upgrade: package libapr1:amd64 is not ready for configuration cannot configure (current status `half-installed')
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apr (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello programmers would like to help me to correct the mistakes that my ubuntu is showing when I do system upgrade and sometimes when I install some programs.
I also want to help me fix the system errors that sometimes stops responding does not work for all programs stop working.
Obrigrado!
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: libapr1:amd64 1.5.1-3
ProcVersionSign
Uname: Linux 3.19.0-37-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Fri Jan 1 14:27:30 2016
DuplicateSignature: package:
ErrorMessage: package libapr1:amd64 is not ready for configuration cannot configure (current status `half-installed')
InstallationDate: Installed on 2015-04-29 (246 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
RelatedPackageV
dpkg 1.17.25ubuntu1.1
apt 1.0.9.7ubuntu4.2
SourcePackage: apr
Title: package libapr1:amd64 1.5.1-3 failed to install/upgrade: package libapr1:amd64 is not ready for configuration cannot configure (current status `half-installed')
UpgradeStatus: Upgraded to vivid on 2015-05-02 (244 days ago)
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.
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.