Comment 72 for bug 450569

Binary package hint: openoffice.org
during a karmic update
ProblemType: Package
Architecture: i386
Date: March 6, 2010
DistroRelease: Ubuntu 9:10
ErrorMessage: E: /var/cache/apt/archives/openffice.org-filter-binfilter_1%3A31.1-ubuntu1.1_i386.deb: subprocess new pre-installation script returned error exit status 1
E: /var/cache/apt/archives/openffice.org-emailmerge_1%3A31.1-ubuntu1.1_i386_all.deb: subprocess new pre-installation script returned error exit status 1
ProcVersionSignature: Ubuntu 2.6.31-20-generic-pae
SourcePackage: openoffice.org
Title: package openoffice.org-emailmerge 1:3.1.1-5ubuntu1
openoffice.org-filter-binfilter, versions 1:3.1.1-5ubuntu1.1
Package Architecture: all
Uname: Linux 2.6.31-20-generic-pae

Verbose:
Karmic upgrade ended with a broken packages in openoffice.org-emailmerge and openoffice.org-filter-binfilter, versions 1:3.1.1-5ubuntu1 and 1:3.1.1-5ubuntu1.1 respectively. When using GUI tools or Command line to fix the broken packages it says, "OpenOffice.org is running right now. A running OpenOffice.org makes extension (de-) registration not possible and it causes problems with (de-) registering components." Before closing the final remarks are: "Processing triggers for libc-bin ... ldconfig deferred processing now taking place..."
Then the error page comes up:
Please close OpenOffice.org (including an eventually running Quickstarter)
Closes with:
E: /var/cache/apt/archives/openffice.org-filter-binfilter_1%3A31.1-ubuntu1.1_i386.deb: subprocess new pre-installation script returned error exit status 1

E: /var/cache/apt/archives/openffice.org-emailmerge_1%3A31.1-ubuntu1.1_i386_all.deb: subprocess new pre-installation script returned error exit status 1

-> for every update or package installation, or broken package fix the entire process above repeats itself.
-> OpenOffice.org nor any of its depends were running at any stage.
->POINT: However, during the first alert for an UPDATE, I had a document open, saved it, closed, returned to the update and clicked "FORWARD." That could have caused the break but in at least 50 times since then I haven't been able to fix the break.