Package: dpkg
Version: 1.17.18
Severity: important

Hi.

This happens since a week or two now,... I'm actually not sure whether it's
dpkg's fault but I have no clue where to start else.

It happens (very often now) that I've upgrade packages via aptitude, see
no error messages during installation, but afterwards, aptitude tells me
something like this:
--- Packages being automatically held in their current state (22)
--- Packages being held back (3)                                                
                                                                                
                              
--\ Packages that are partially installed (8)
T    cups                                                                       
                                                                                
 1.7.5-4+b1     1.7.5-4+b1
W A  cups-filters                                                               
                                                                                
 1.0.61-2       1.0.61-2
T    gxine                                                                      
                                                                                
 0.5.908-3      0.5.908-3
W A  libxine2-ffmpeg                                                            
                                                                                
 1.2.6-1+b2     1.2.6-1+b2
W A  libxine2-gnome                                                             
                                                                                
 1.2.6-1+b2     1.2.6-1+b2
W A  libxine2-misc-plugins                                                      
                                                                                
 1.2.6-1+b2     1.2.6-1+b2
W A  libxine2-x                                                                 
                                                                                
 1.2.6-1+b2     1.2.6-1+b2
T    xine-ui                                                                    
                                                                                
 0.99.9-1.1     0.99.9-1.1


(And I've never seen T and W states before ^^).

The above state was after todays upgrades, the log of that upgrade run (i.e.
before it showed the above) is attached as aptitutde.log.1.


If I now press g again in aptitude, and make a new pass of running apt/dpkg
(without installations) nothing is changed (i.e. it doesn't try to
reconfigure the above as it normally does when packages are left in a broke
state).


Then I try a
dpkg --configure -a
and ... oh *suprised* (I'm really just doing this while writing, and this
time I got errors there)... I get what's in dpkg-configure-a.log
The last time I saw such T / W state packages (but then it were usually just
1 or 2)... dpkg --configure -a simply run without any visible errors
and the obove packages were again back to okay in aptitude.


Okay I try a bit more now, i.e:
# dpkg --configure xine-ui
dpkg: error processing package xine-ui (--configure):
 package xine-ui is already installed and configured
Errors were encountered while processing:
 xine-ui
# dpkg --configure gxine
dpkg: error processing package gxine (--configure):
 package gxine is already installed and configured
Errors were encountered while processing:
 gxine
# dpkg --configure gnome-menus
Setting up gnome-menus (3.13.3-2) ...
# dpkg --configure debian-security-support
Setting up debian-security-support (2014.09.07) ...
# dpkg --configure cups
dpkg: error processing package cups (--configure):
 package cups is already installed and configured
Errors were encountered while processing:
 cups


After this I tried another:
# dpkg --configure -a
#

this time it "worked" apparently...

And there are no longer any packages marked W or T in aptitude.


So it seems something is broken here with the triggers?


Any ideas what to do?

I don't think that there is any filesystem corruption (or any hardware
corruption),... neither would I've had any system crash or non-clean
shutdown for... well I guess more than half a year, that could perhaps
have corrupted any of dpkg's or APT's state files.


Cheers,
Chris.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to