[Bug 503765] Re: aptitude pkgstates gets corrupted
503765 at bugs.launchpad.net
Tue Sep 4 10:34:59 UTC 2012
On 4 September 2012 17:41, Sergio Callegari <sergio.callegari at gmail.com> wrote:
> If I clean up the scheduled changes in aptitude, then I work for some
> time (say 1 month) without using aptitude, but just apt-get, synaptic,
> or apper and after 1 month I go back to saying 'sudo aptitude install',
> then aptitude shows that mess, probably due to the fact that it is being
> confused by something that happened behind it shoulders.
Curious. I have absolutely never experienced that although I do
intermix use of apt-get with aptitude. There are reports of small
scale problems like this, but they only ever have mentioned one or two
packages which were previously installed/removed by aptitude. I will
attempt to recreate this and look in to it.
Do you have something like apticron or cron-apt installed which may be
scheduling updates with aptitude?
Please attach also the output from:
$ sudo apt-config dump -c /root/.aptitude/config -c ~/.aptitude/config
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to aptitude in Ubuntu.
aptitude pkgstates gets corrupted
Status in “aptitude” package in Ubuntu:
Binary package hint: aptitude
On four different machines (one 32 bit, two 64bit), I am recently
experiencing corruptions in the package status database private to
aptitude, namely /var/lib/aptitude/pkgstates.
This results in a crazy behavior of aptitude, that starts thinking
that many packages are broken when in fact they are not. For
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages are BROKEN:
apturl gnome-app-install libgpod4 libgpod4-nogtk mysql-server-core-5.1 rsyslog wine1.2
The following NEW packages will be installed:
acl binutils-static emacs22 emacs22-bin-common emacs22-common firefox-3.0-branding gcj-4.3
gfortran-4.3 gij gnome-mount imagemagick-doc klogd libavutil-unstripped-49
libboost-regex1.34.1 libboost-serialization1.34.1 libfame-0.9 libgcj9-0-awt libgcj9-dev
libggi-target-x libggi2 libgii1 libgii1-target-x libgmyth0 liblrdf0 libpolkit-gnome0
libpvm3 libsmbios2 libsoprano-dev libwxbase2.6-0 libwxgtk2.6-0 mysql-server-core-5.0
nvidia-180-kernel-source nvidia-180-libvdpau policykit-gnome pvm python-gconf
python-gst0.10 python-launchpad-integration python-pyorbit python-sexy sysklogd
ttf-bengali-fonts ttf-kannada-fonts ttf-oriya-fonts ttf-telugu-fonts update-motd wine
This is very very dangerous, because, following up with its crazy
diagnosis, aptitude starts suggesting actions that can completely
break a system.
And the crazyness of aptitude can be very easily seen by considering
that for apt-get, synaptic and all the other front-ends to dpkg
everything is just fine.
Interestingly, aptitude starts reporting as broken either packages
that are installed and packages that are not installed. If one tries
aptitude remove <package that is not installed but is reported as
then aptitude does nothing, but the behavior of aptitude after this
sanifies a bit.
removing /var/lib/aptitude/pkgstates completely fixes the issue.
In the "wrong" pkgstates, it looks like many entries are just weird.
For instance, installed packages are indicated as unseen, and after
pkgstates is removed and re-generated, for many packages the state is
I tend to think that bug reports 477468 and 39497 are in fact caused by this very problem, so I suggest marking those as duplicate of this one.
Date: Wed Jan 6 12:47:37 2010
DistroRelease: Ubuntu 9.10
Package: aptitude 0.4.11.11-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
Uname: Linux 2.6.31-16-generic x86_64
To manage notifications about this bug go to:
More information about the foundations-bugs