Ubuntu
nspluginwrapper package

package nspluginwrapper 1.2.2-0ubuntu9 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 139 terug

Bug #782745 reported by Maria HendrickxO34494445 on 2011-05-14

This bug report is a duplicate of: Bug #773020: nspluginwrapper segfaults in post-install script. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	nspluginwrapper (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: nspluginwrapper

With the upgrade this software gave an error. I do not know why.
I also saw I have no keyboard in the browser. But in Libreoffice the keyboard works.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: nspluginwrapper 1.2.2-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4
Uname: Linux 2.6.38-9-generic x86_64
AptOrdering:
adept: Install
nspluginwrapper: Configure
flashplugin-installer: Configure
acroread: Configure
adept: Configure
Architecture: amd64
Date: Sat May 14 20:00:01 2011
ErrorMessage: subproces installed post-installation script gaf een foutwaarde 139 terug
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: nspluginwrapper
Title: package nspluginwrapper 1.2.2-0ubuntu9 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 139 terug
UpgradeStatus: Upgraded to natty on 2011-05-14 (0 days ago)

Tags:

Revision history for this message

Maria HendrickxO34494445 (mar-hendrickx) wrote on 2011-05-14:

Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
Df.txt Edit (392 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (44.3 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (705 bytes, text/plain; charset="utf-8")

Revision history for this message

Robert Roth (evfool) wrote on 2011-05-19:

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.