Issue 123208 - Repair AOO fails with error message "Close Quick Starter ..."
Summary: Repair AOO fails with error message "Close Quick Starter ..."
Status: CLOSED OBSOLETE
Alias: None
Product: Installation
Classification: Application
Component: ui (show other issues)
Version: 4.0.1-dev
Hardware: PC Windows 7
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-07 06:08 UTC by Rainer Bielefeld
Modified: 2016-11-09 13:43 UTC (History)
6 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Bielefeld 2013-09-07 06:08:56 UTC
Steps how to reproduce Reproducible with  "AOO 4.0.1 – German UI / German locale  [AOO401m3(Build:9712)  -  Rev. 1520285 2013-09-05 13:52:01]" on German German WIN7 Home Premium (64bit)", Common 4.0-dev User Profile

1. With installed AOO 4.0.0, do Custom installation for all users, 
   Additional components ActiveX and  XSLT Filters, No Quickstarter, 
   Not for MSO documents, without more frills
2. Launch AOO 4.0.1 from Desktop Icon
   > WIN Task manager will show soffice.bin and soffice.exe
3. Close AOO 4.0.1
   > office.bin and soffice.exe vanish from WIN Task manager 
4. In WIN System administration "Modify or uninstall Program" try to Repair
   AOO 4.0.1 with click on "Repair" button with selected AOO 4.0.1
   Expected: run through alll installation steps
   Actual: fails with message "Quit AOO 4.0.1 and Quickstarter ..."     :-(
           But There is no quick starter active and no soffice in
           WIN Task manager

Additional information
----------------------
a) Repair via 'Modify' button will work fine
b) Remove (uninstall) works fine
Comment 1 Edwin Sharp 2013-09-08 06:36:32 UTC
No problem with Rev. 1520602 Win 7

Differences from original description:
2.4.3 instead 4.0.0
Default instead Custom installation
Only for me instead for all users
Comment 2 billp 2013-10-20 19:07:46 UTC
I do see the problem on 64-bit Windows 8.1. I had installed AOO 4.0.1 (EN-US) using a typical installation with a new user profile (no profile imported from previous version). Upon starting Writer, "OpenOffice 4.0.1 (32 bit) was shown in the Task Manager on the Processes tab in the Apps list and the Background processes list. On the Details tab of Task Manager, soffice.bin, soffice.exe and swriter.exe appeared. When Writer was closed, AOO no longer appeared as a running App or Background process and soffice.bin, soffice.exe and swriter.exe no longer appeared on the Details tab.

When OpenOffice 4.0.1 was selected in "Uninstall or change a program" and the Repair option was selected, the message "Please exit OpenOffice 4.0.1 and the OpenOffice 4.0.1 Quickstarter..." appeared with an OK button. Pressing the OK button resulted in a message "Fatal error during installation."

When OpenOffice 4.0.1 was selected in "Uninstall or change a program" and the Change option was selected, the OpenOffice 4.0.1 - Installation Wizard appeared with options to Modify, Repair, or Remove. After selecting Repair, the Installation Wizard produced a message that Firefox was using files that needed to be updated and to close Firefox and retry. After closing Firefox and clicking "Retry" the repair proceeded normally.

When OpenOffice 4.0.1 was selected in "Uninstall or change a program" and the Uninstall option was selected, uninstall was normal with no message to exit OOo.
Comment 3 Evan Burkitt 2014-05-14 20:21:27 UTC
On 64-bit Windows 7 I experienced this problem attempting to upgrade from 4.0.1 to 4.1.0. I was unable to uninstall the old version, either, due the the same error. I used Sysinternals' Process Explorer to search for "OpenOffice" in the file path of loaded DLLs and found that the Flash plugin in Firefox had a DLL in the OO installed path open. After closing FireFox I was able to complete the upgrade.

During my search for a solution I discovered that earlier OO installers encountering this problem would actually give the name and ID of the process holding the open handle. I vote for this behavior to be restored. If that's not acceptable then at least write the information into an installer log.
Comment 4 oooforum (fr) 2016-11-09 09:37:51 UTC
.