package openoffice.org-emailmerge 1:3.2.0~rc4-1ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Bug #545241 reported by
Matt
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 10 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openoffice.org (Ubuntu) |
Triaged
|
High
|
Chris Cheney |
Bug Description
Binary package hint: openoffice.org
Upgrade fails in lucid.
ProblemType: Package
Architecture: i386
Date: Tue Mar 23 16:09:53 2010
DistroRelease: Ubuntu 10.04
ErrorMessage: subprocess new pre-installation script returned error exit status 1
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: openoffice.
PackageArchitec
ProcVersionSign
SourcePackage: openoffice.org
Title: package openoffice.
Uname: Linux 2.6.32-16-generic i686
To post a comment you must log in.
This is caused by:
check_for_ running_ ooo() { openoffice/ program/ bootstraprc ]; then
LOCKFILE= "`grep UserInstallation /usr/lib/ openoffice/ program/ bootstraprc | cut -d= -f2 | sed -e 's,SYSUSERCONFI G,HOME, '`/.lock"
PID=` pgrep soffice.bin | head -n 1`
if [ "$DEBIAN_FRONTEND" = "noninteractive" ]; then
echo "OpenOffice.org running!" >&2
echo "" >&2
echo -n "OpenOffice.org is running right now with pid " >&2
echo -n "$PID." >&2
echo " This can cause problems" >&2
echo "with (de-)registration of components and e
echo "Thus this package will fail to install" >&2
echo "You should close all running instances of OpenOffice.org (including" >&2
echo "any currently running Quickstarter) before proceeding with the package" >&2
echo "upgrade." >&2
exit 1
else
db_ input high shared/ openofficeorg- running || true
db_ go || true
# try again in case OOo got closed before hitting OK
PID= `pgrep soffice.bin | head -n 1`
if [ -n "$PID" ] || [ -e "$LOCKFILE" ]; then
exit 1
fi
fi
if [ -e /usr/lib/
if [ -n "$PID" ] || [ -e "$LOCKFILE" ]; then
xtensions" >&2
fi
fi
}
If OOo can't be safely upgraded while running, aborting the upgrade doesn't seem like the ideal way to handle this. Alternatives:
- Just go ahead, and warn the user that they need to take action (as Firefox does)
- Keep checking until the user has closed the application
- Work around whatever breakage happens if it's upgraded in place