Ubuntu
syscp package

package syscp 1.4.2.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #670152 reported by Marijan Vidic on 2010-11-02

This bug report is a duplicate of: Bug #595015: package syscp 1.4.2.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: syscp

Using ubuntu software center to instal lamp server and than in progres it reports error trying to instal last 2 databases

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: syscp 1.4.2.1-2
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Tue Nov 2 22:51:26 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
SourcePackage: syscp
Title: package syscp 1.4.2.1-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Marijan Vidic (bmbiroservis) wrote on 2010-11-02:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (672 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (46.2 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (9.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Victor Vargas (kamus) wrote on 2011-07-15:

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