package syslinux-themes-debian 12-3 failed during upgrade from 14.04 to 14.10: subprocess installed post-removal script returned error exit status 127

[Chris Cook]

I have upgraded three systems from Xubuntu 14.04 to 14.10. the first was an Acer Aspire One 753 (64bit, one display) that had no problems.

The other two (also 64bit dual monitor setups) through up this error. The other dual monitor system I did not report a bug and finished the upgrade. It has a problem when I disconnet one of the displays (and the mouse and keyboard) via a kwm switch. xfsettngd crashes and the icons change in the menus until it is restarted. I expect this system will do the same after the upgrade is finished. Watch this space.

This is similar to ​ bug #1365657 and #1385605 but I think there are 32bit systems, this is a 64bit system.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: syslinux-themes-debian 12-3
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Wed Oct 29 18:27:38 2014
Dependencies:

DuplicateSignature: package:syslinux-themes-debian:12-3:subprocess installed post-removal script returned error exit status 127
ErrorMessage: subprocess installed post-removal script returned error exit status 127
InstallationDate: Installed on 2014-09-13 (46 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
SourcePackage: syslinux-themes-debian
Title: package syslinux-themes-debian 12-3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 127
UpgradeStatus: Upgraded to utopic on 2014-10-29 (0 days ago)

[Chris Cook (ccook1962)]

It appears the xfsettngd crashes are unrelated I will investigate those further.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1365657, so 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.