Ubuntu
mono package

package monodoc-base 2.6.7-5ubuntu3 failed to install/upgrade: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

Bug #936730 reported by philippe on 2012-02-20

This bug report is a duplicate of: Bug #772482: package monodoc-base 2.6.7-5ubuntu3 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

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

Bug Description

ras

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: monodoc-base 2.6.7-5ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-32.65-generic 2.6.35.14
Uname: Linux 2.6.35-32-generic i686
Architecture: i386
Date: Mon Feb 20 01:56:06 2012
ErrorMessage: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
PackageArchitecture: all
SourcePackage: mono
Title: package monodoc-base 2.6.7-5ubuntu3 failed to install/upgrade: ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
UpgradeStatus: Upgraded to natty on 2012-02-19 (0 days ago)

Tags:

Revision history for this message

philippe (spip) wrote on 2012-02-20:

Dependencies.txt Edit (1.7 KiB, text/plain; charset="utf-8")
VarLogDistupgradeAptlog.gz Edit (8.5 KiB, application/x-gzip)
VarLogDistupgradeApttermlog.gz Edit (19.4 KiB, application/x-gzip)
VarLogDistupgradeHistorylog.gz Edit (25.3 KiB, application/x-gzip)
VarLogDistupgradeLspcitxt.gz Edit (596 bytes, application/x-gzip)
VarLogDistupgradeMainlog.gz Edit (16.5 KiB, application/x-gzip)
VarLogDistupgradeTermlog.gz Edit (14.6 KiB, application/x-gzip)

Revision history for this message

Sami Jaktholm (sjakthol) wrote on 2013-12-25:

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