Ubuntu
openoffice.org package

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

Bug #534648 reported by Gottfried Freudenberger on 2010-03-08

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)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: openoffice.org

Error Report when re-booting after update to Kernel 2.6.31.20. OOO not started. Do not understand the background of the message.

ProblemType: Package
Architecture: i386
Date: Mon Mar 1 22:09:38 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: openoffice.org-emailmerge 1:3.1.1-5ubuntu1.1
PackageArchitecture: all
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: openoffice.org
Title: package openoffice.org-emailmerge 1:3.1.1-5ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Uname: Linux 2.6.31-20-generic i686

Tags:

Revision history for this message

Gottfried Freudenberger (freugo) wrote on 2010-03-08:

AptOrdering.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (4.1 KiB, text/plain; charset="utf-8")
Dmesg.txt Edit (42.9 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (9.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Mitch Towner (kermiac) wrote on 2010-03-09:

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