package irqbalance 1.0.6-3ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This bug report was converted into a question: question #273167: package irqbalance 1.0.6-3ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
irqbalance (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
package failed to install for unknown reason
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: irqbalance 1.0.6-3ubuntu1.1
Uname: Linux 3.19.3-
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
Date: Thu Sep 24 15:28:56 2015
DuplicateSignature: package:
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-02-27 (574 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
RelatedPackageV
dpkg 1.17.25ubuntu1
apt 1.0.9.7ubuntu4.1
SourcePackage: irqbalance
Title: package irqbalance 1.0.6-3ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to vivid on 2015-04-24 (153 days ago)
tags: | removed: need-duplicate-check |
Changed in irqbalance (Ubuntu): | |
status: | Incomplete → Invalid |
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.