Ubuntu
openoffice.org package

package openoffice.org-emailmerge 1:3.1.1-5ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

Bug #527134 reported by henry_the_horse on 2010-02-24

This bug report is a duplicate of: Bug #450569: [Master] package openoffice.org-emailmerge 1:3.2.0-7ubuntu4.1 failed to install/upgrade:. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	openoffice.org (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: openoffice.org

This is the same error and situation previously reported in other "package openoffice.org-emailmerge 1:3.1.1-5ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1" bugs. But I wanted to specify I'm using Ubuntu 9.10 x86-64.

ProblemType: Package
Architecture: amd64
Date: Wed Feb 24 09:10:55 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: vmnet vmci vmmon
Package: openoffice.org-emailmerge 1:3.1.1-5ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: openoffice.org
Title: package openoffice.org-emailmerge 1:3.1.1-5ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Uname: Linux 2.6.31-19-generic x86_64

Tags:

Revision history for this message

henry_the_horse (jmsteward) wrote on 2010-02-24:

AptOrdering.txt Edit (929 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (58.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (39.6 KiB, text/plain; charset="utf-8")

Revision history for this message

Monkey (monkey-libre) wrote on 2010-02-24:

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 #526876, 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.