package syslinux-themes-debian 12-3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 127

[Charly]

upgrading 14.04 to 14.10

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: syslinux-themes-debian 12-3
ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
Uname: Linux 3.13.0-34-generic i686
ApportVersion: 2.14.7-0ubuntu2
Architecture: i386
Date: Thu Sep 4 14:52:23 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-08-13 (22 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
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-09-03 (1 days ago)

[Launchpad Janitor (janitor)]

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

[David Jones (dwrj87-deactivatedaccount-deactivatedaccount-deactivatedaccount)]

In the process of upgrading to 14.10 using update-manager -d, and this came up near the end, after asking me to remove obsolete software

[Mark Rich (sir-marky)]

This has just happened to me post installation to 14.10 using,

sudo do-release-upgrade

[Brice Terzaghi (terzag)]

Got this problem too on one of my PCs (upgraded two of them from 14.04 to 14.10). The one not affected probably didn't have this package installed. On the one affected, I think it was installed for Unetbootin.

[Julio (julio7k)]

got the same issue, unebooting was installed, ran sudo apt-get remove --purge syslinux-themes-debian and reinstalled without issues.

[Jean-Max Reymond (jmreymond-free)]

thanks to Julio, apt-get remove and apt-get install works

[ScarySquirrel (coproc-sbcglobal)]

ran sudo apt-get remove --purge syslinux-themes-debian and reinstalled without issues, too.

I also got an issue with my installation of redmine, but that will have to be for a different bug.

[Ephraim Gadsby Jr. (ephraimgadsbyjr)]

Julio,
        You are the man! It worked on my 14.04->14.10 upgrade. Thanks for the help!
  Peace....Ephraim

[Opiwa (nicotiane-launchpad)]

ran "sudo apt-get remove --purge syslinux-themes-debian ; sudo apt-get install syslinux-themes-debian " without issues, too.

[EKaroline Jones (ekj1237)]

Learning, and want to run different linux os from virtual environment...to test compatibility with Acer-Aspire/Intel processor, Netbook..., Ubuntu 14.10 lts may be too, heavy, screen freezes alot when using Ubuntu Software Center. Thank you.

[EKaroline Jones (ekj1237)]

Reloaded Ubuntu to my netbook many times to see if this would fix problems, desktop freezes.

[Brice Terzaghi (terzag)]

I'm not sure your problem has anything to do with this particular bug report...

[Jonas Kolben (jonas-kolben)]

ran "sudo apt-get remove --purge syslinux-themes-debian ; sudo apt-get install syslinux-themes-debian " without issues, too.

[inneas (inneas)]

Same issue here on 14.04 without upgrade to 14.10.
Installed and removed unetbootin. Then apt-get autoremove failed to remove syslinux-themes-debian with exit status 127 from the post-removal script.

[Mark Walters (markwalt)]

Had same problem. Ran sudo apt-get remove --purge syslinux-themes-debian; then reinstalled. Problem cleared up.

My system was a clean install of Xubuntu 14.04 from the "minimal install" CD since it couldn't boot off of flash drive, and I didn't have a DVD-R handy at install time. I subsequently upgraded to 14.10 with do-release-upgrade and got the error.

[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.