package syslinux-themes-debian 12-3 failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed »)

[Jean-Max Reymond]

message when rebooting a blocked system

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: syslinux-themes-debian 12-3
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
AptOrdering: syslinux-themes-debian: Configure
Architecture: amd64
Date: Sat Oct 25 10:10:00 2014
DpkgTerminalLog:
 dpkg: erreur de traitement du paquet syslinux-themes-debian (--configure) :
  le paquet syslinux-themes-debian n'est pas prêt pour la configuration
  configuration impossible (état actuel « half-installed »)
DuplicateSignature: package:syslinux-themes-debian:12-3:le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed »)
ErrorMessage: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed »)
InstallationDate: Installed on 2014-04-18 (195 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: syslinux-themes-debian
Title: package syslinux-themes-debian 12-3 failed to install/upgrade: le paquet syslinux-themes-debian n'est pas prêt pour la configuration configuration impossible (état actuel « half-installed »)
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robie Basak (racb)]

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 1042511, 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.