Ubuntu
adobereader-deu package

package adobereader-deu 9.3.1-2 [modified: opt/Adobe/Reader9/Reader/GlobalPrefs/.config] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 zurück

Bug #558988 reported by holimatic on 2010-04-09

This bug report is a duplicate of: Bug #551941: package adobereader-deu 9.3.1-2 [modified: opt/Adobe/Reader9/Reader/GlobalPrefs/.config] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 zurück. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	adobereader-deu (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: adobereader-deu

Error occured during update

ProblemType: Package
Architecture: i386
Date: Fri Apr 9 08:28:48 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 zurück
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: adobereader-deu 9.3.1-2 [modified: opt/Adobe/Reader9/Reader/GlobalPrefs/.config]
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic-pae
SourcePackage: adobereader-deu
Title: package adobereader-deu 9.3.1-2 [modified: opt/Adobe/Reader9/Reader/GlobalPrefs/.config] failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 10 zurück
Uname: Linux 2.6.31-20-generic-pae i686

Tags:

Revision history for this message

holimatic (guido-hollenstein) wrote on 2010-04-09:

AptOrdering.txt Edit (829 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (2.9 KiB, text/plain; charset="utf-8")
Dmesg.gz Edit (19.6 KiB, application/x-gzip)
DpkgTerminalLog.txt Edit (11.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2010-04-09:

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 551941, 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.