package nspluginwrapper 1.2.2-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Marcus Wanner]

Binary package hint: nspluginwrapper

Can't install after 11.04 upgrade; Segfaults when trying. Had 4.0 release, prerelease, and beta installed before upgrade.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: nspluginwrapper 1.2.2-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
AptOrdering:
 nspluginwrapper: Configure
 flashplugin-installer: Configure
 flashplugin-nonfree: Configure
Architecture: amd64
Date: Sun May 1 07:24:31 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 139
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
SourcePackage: nspluginwrapper
Title: package nspluginwrapper 1.2.2-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
UpgradeStatus: Upgraded to natty on 2011-04-30 (0 days ago)

[mcNisse (johan-erlands)]

Googletalk plugin causes nspluginwrapper to crash.

As a workaround you can unstall it.

[BryanFRitt (bryanfritt)]

removing Googletalk fixed it for me,
Afterwards I installed flashplugin64-installer, and then put back google-talkplugin.
(Hadn't tested google-talkplugin, but the acroread, and flash seams to work)

[Marcus Wanner (marcusw-cox)]

Yeah, removing google-talkplugin seems to fix this. Looks like someone just broke every single ubuntu natty with both flash and Google Talk installed. I wonder how this wasn't found in testing? Maybe the 6-month release cycle is too short?

[Robert Roth (evfool)]

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 #769721, 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. Feel free to continue to report any other bugs you may find.