package timidity 2.13.2-37 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting a removal.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
timidity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: timidity
Description: Ubuntu 10.04.2 LTS
Release: 10.04
timidity:
Installed: 2.13.2-37
Candidate: 2.13.2-37
Version table:
*** 2.13.2-37 0
500 http://
100 /var/lib/
I attempted to install the package. It repeatedly hung during the installation process. I used apt package manager to upgrade the package.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: timidity 2.13.2-37
ProcVersionSign
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelMo
AptOrdering:
timidity: Remove
libc-dev-bin: Install
libc-dev-bin: Configure
Architecture: amd64
CheckboxSubmission: 73c1a3309264f88
CheckboxSystem: da9af3b901b5569
Date: Sun Feb 13 13:42:43 2011
DpkgTerminalLog:
Log started: 2011-02-13 13:42:42
dpkg: error processing timidity (--remove):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
ErrorMessage: Package is in a very bad inconsistent state - you should reinstall it before attempting a removal.
SourcePackage: timidity
Title: package timidity 2.13.2-37 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting a removal.
Thanks for reporting this bug, and sorry about the trouble. I realize this was a long time ago, but do you still have logs of the terminal output when installing timidity? If you're lucky, one of the /var/log/ apt/term. log.*.gz files has it -- try "zgrep timidity /var/log/ apt/term. log.*.gz" . Please attach that file, if you still have it.
It also looks like you have a locally-modified ALSA installation. Is this intentional, and did you change anything in particular there? I've seen a couple of other bugs where the timidity-daemon initscript will crash if ALSA is configured incorrectly (and so the daemon cannot start).