Ubuntu
language-selector package

package language-selector-common 0.6.7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

Bug #766621 reported by PhilippeSeidel on 2011-04-19

This bug report is a duplicate of: Bug #766534: Regression on maverick when updating to 0.6.7 (security upload). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	language-selector (Ubuntu)	Fix Released	Undecided	Unassigned

Bug Description

Binary package hint: language-selector

I couldn't see what actually was wrong, but the error happened while updating to the newest version

ProblemType: Package
DistroRelease: Ubuntu 10.10
Package: language-selector-common 0.6.7
ProcVersionSignature: Ubuntu 2.6.35-28.50-generic 2.6.35.11
Uname: Linux 2.6.35-28-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Apr 19 23:42:09 2011
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück
PackageArchitecture: all
SourcePackage: language-selector
Title: package language-selector-common 0.6.7 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

Revision history for this message

PhilippeSeidel (pagin) wrote on 2011-04-19:

AptOrdering.txt Edit (473 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (701 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (73.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (47.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Benjamin Kerensa (bkerensa) wrote on 2011-04-19:

Yeah this happened to me today too and a number of other people I can see multiple bug reports for the same issue.

Changed in language-selector (Ubuntu):
status:	New → Confirmed
status:	Confirmed → Fix Released

Revision history for this message

Benjamin Kerensa (bkerensa) wrote on 2011-04-19:

Just compared this bug to a number of others and it looks like a fix was just released so you can attempt to run a new update to resolve this. I have marked this this report as a duplicate and changed status to match source report.