Ubuntu
openoffice.org package

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

Bug #515840 reported by Darkmike on 2010-02-02

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 5 people

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

Bug Description

Binary package hint: openoffice.org

That bug apend when i try to remove openoffice-core package.

thx

ProblemType: Package
Architecture: amd64
Date: Mon Feb 1 23:07:24 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed pre-removal script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: openoffice.org-emailmerge 1:3.1.1-5ubuntu1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-18.55-generic
SourcePackage: openoffice.org
Title: package openoffice.org-emailmerge 1:3.1.1-5ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Uname: Linux 2.6.31-18-generic x86_64

Tags:

Revision history for this message

Darkmike (mikefaille) wrote on 2010-02-02:

AptOrdering.txt Edit (492 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (755 bytes, text/plain; charset="utf-8")
Dmesg.gz Edit (29.0 KiB, application/x-gzip)
DpkgTerminalLog.gz Edit (43.9 KiB, application/x-gzip)

Revision history for this message

Karl (karel2) wrote on 2010-02-24:

I got a similar error message, however I noticed that OpenOffice was open and I was using it at the same time as I received the error message.

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.