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 #528426 reported by Enri on 2010-02-26

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 1 person

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

Bug Description

Binary package hint: openoffice.org

A message pop up asking me to report the bug. I have an open office doc running o.k., so maybe is from a previous session.

ProblemType: Package
Architecture: i386
Date: Fri Feb 26 07:45:08 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: wl
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 i686

Tags:

Revision history for this message

Enri (enriquedelapena) wrote on 2010-02-26:

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

Revision history for this message

Victor Vargas (kamus) wrote on 2010-02-26:

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