Ubuntu
postgresql-8.4 package

package postgresql-8.4 8.4.6-0ubuntu10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #701253 reported by Nik Sheridan on 2011-01-10

This bug report is a duplicate of: Bug #264336: pgsql fails to start due to shared buffer setting greater than kernel allows. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	postgresql-8.4 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: postgresql-8.4

Installing software (cheese) that appears to want to use this SQL service but it fails for an unlisted reason

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: postgresql-8.4 8.4.6-0ubuntu10.04
ProcVersionSignature: Ubuntu 2.6.32-27.49-generic 2.6.32.26+drm33.12
Uname: Linux 2.6.32-27-generic i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sat Jan 8 14:25:10 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
SourcePackage: postgresql-8.4
Title: package postgresql-8.4 8.4.6-0ubuntu10.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Nik Sheridan (nik-sheridan) wrote on 2011-01-10:

Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (518 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (55.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (59.9 KiB, text/plain; charset="utf-8")

Revision history for this message

Brian Murray (brian-murray) wrote on 2011-07-27:

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