Package xxxxx is already installed and configured

Hmm iucode-tool was clearly installed in the last packaging run, see AptTermLog:

Preparing to unpack .../iucode-tool_1.1.1-1_i386.deb ...
Unpacking iucode-tool (1.1.1-1) ...
Selecting previously unselected package intel-microcode.
Preparing to unpack .../intel-microcode_3.20150121.1_i386.deb ...
Unpacking intel-microcode (3.20150121.1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Setting up iucode-tool (1.1.1-1) ...
Setting up intel-microcode (3.20150121.1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Processing triggers for initramfs-tools (0.103ubuntu15) ...
update-initramfs: Generating /boot/initrd.img-3.19.0-15-generic
Log ended: 2015-04-21 23:52:06

@Brian

My two cents about such bug: " package xxxx is already installed and configured "
- it have been seen at least since Precise
- Apport blame dpkg
- but i'm using 'synaptic' instead of the now defaulted 'software-center' in ubuntu, and never met such a bug on my systems
- as i understand, when a package is installed & configured, its status is not updated as expected

So Software-center, or one of its dependencies, should be blamed instead of dpkg. Those are never fixed and upstream never know about them.
Apport wrongly blame dpkg, and does not understand the repeating " package xxxx is already installed and configured " and is disturbed by the package name, which can be randomly every package in the archive. So it never detect duplicates in such a case.

Looks like the now applied tests have missed such a possiblity.

Debian comment:

From: Guillem Jover <email address hidden>
To: Alberto Salvia Novella <email address hidden>, <email address hidden>

I think this and the ton of duped bugs in Launchpad are just a symptom of a buggy frontend asking dpkg to install packages multiple times, which then dpkg complains about.

I'm assuming that the package is actually properly configured on the system, and the problem comes from whatever frontend is being used in Ubuntu.

@Adolfo

please read #4 above to understand that the package name does not matter here; and dpkg is not to blame as explained by Debian dev. Its a pure Ubuntu problem when Software-center is used as its so badly designed, buggy and quite not maintained.
So please dont mess up the changes i've made till you really motivate yours.

add update-manager as it can be concerned