package iptraf 3.0.0-7 failed to install/upgrade: package iptraf is already installed and configured

Bug #697819 reported by Yang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: dpkg

I don't know what caused this. sudo iptraf seems to run fine.

I had installed iptraf earlier in the day, then rebooted my computer. After the reboot, that's when I noticed the exclamation mark/exploding star icon in the tray (it may have been there earlier).

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: iptraf 3.0.0-7
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering:
 nethogs: Install
 iptraf: Configure
 nethogs: Configure
Architecture: amd64
Date: Tue Jan 4 11:04:58 2011
ErrorMessage: package iptraf is already installed and configured
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: dpkg
Title: package iptraf 3.0.0-7 failed to install/upgrade: package iptraf is already installed and configured

Revision history for this message
Yang (yaaang) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach /var/log/apt/history.log ?

Revision history for this message
Yang (yaaang) wrote :

Here you go. This was generated with:

cd /var/log/apt/
for i in 10 9 8 7 6 5 4 3 2 1 ; do zcat history.log.$i.gz ; done | cat - history.log | gzip > /tmp/history.log.gz

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks a lot for this data!

Here is where the error happend:

Start-Date: 2011-01-04 11:04:44
Install: nethogs (0.7.0-3)
Error: Sub-process /usr/bin/dpkg returned an error code (1)
End-Date: 2011-01-04 11:04:59

What is confusing in the terminal log is that apparently apt wanted to configure iptraf but there
is nothing in the logs that indicate that it needs configuring (i.e. the previous operation seems
to have completed just fine):
"""
Log started: 2011-01-04 11:04:14
Selecting previously deselected package iptraf.
Unpacking iptraf (from .../iptraf_3.0.0-7_amd64.deb) ...
Processing triggers for doc-base ...
Processing 1 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for man-db ...
Setting up iptraf (3.0.0-7) ...

Log ended: 2011-01-04 11:04:41

Log started: 2011-01-04 11:04:44
Selecting previously deselected package nethogs.
(Reading database ... 306757 files and directories currently installed.)
Unpacking nethogs (from .../nethogs_0.7.0-3_amd64.deb) ...
Processing triggers for man-db ...
dpkg: error processing iptraf (--configure):
 package iptraf is already installed and configured
Setting up nethogs (0.7.0-3) ...
"""

Revision history for this message
Michael Vogt (mvo) wrote :

It looks like it was a one-time-only-error, right? I.e. it did not hapen on the subsequent runs of apt?

One possible explaination could be that the man-db trigger lead apt to believe that the iptraf package needs configuration. This would explain why it was a one-time-only issue (if it was one) as the subsequent nethogs install activated the trigger and caused the problem to go away.

Revision history for this message
Yang (yaaang) wrote :

Yeah I guess it never came up again...

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 541595, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.