Ubuntu
phpbb3 package

package phpbb3 3.0.4-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #672695 reported by Daan Hoogland on 2010-11-08

This bug report is a duplicate of: Bug #410888: package phpbb3 3.0.4-0ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1. Edit Remove

This bug affects 1 person

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

Bug Description

Binary package hint: phpbb3

Maybe the installation failed because I did, and still do, not know what database to choose afterwards.

I am using Ubuntu 10.04

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: phpbb3 3.0.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Sun Nov 7 11:12:14 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: phpbb3
Title: package phpbb3 3.0.4-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Daan Hoogland (dhoogland) wrote on 2010-11-08:

AptOrdering.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
Df.txt Edit (450 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (47.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (8.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Laurent Bigonville (bigon) wrote on 2011-08-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 410888, 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.