Description: See attachment. This report relates to the smaller popup shown, about requiring a reboot. 1. A different message to this effect (reboot required) appears after the installer finishes, so the message dealt with here should probably not appear at all. If the above is accepted, the below can be ignored. 2. Some seconds after okaying one such window, another one popped up. Regardless of how many reasons for rebooting are encountered, the user only cares to see one such message. 3. The Cancel button - would pressing it cancel the installation process? Not clear (nothing in the text refers to it). 4. The OK button - would pressing it cause an immediate reboot? Not clear (the text is confusing in this regard). 5. The Cancel button should probably not be there, unless it serves a purpose other than aborting the installation process. There is already such funcationality available in the installer window itself (see the larger windows in the attachment). Actual Results: See Description. Expected Results: See Description. Reproducible: Didn't try User Profile Reset: No Additional Info: Installing v6.4.5.2 with 6.3.2.2 already installed.
Created attachment 163358 [details] This shouldn't appear.
Created attachment 163359 [details] This is good - appears after the installer finishes.
No, IIUC they are correct as implemented, and both needed with MS Installer (MSI) packaging tasks. The first occurs before any changes have been made--allowing you to abort either the blocking processes or end the installation. The second after the installation/update has occurred and is needed to complete the MSI installer actions.
(In reply to V Stuart Foote from comment #3) Absolutely correct. The first allows user to choose not to perform an installation in case when it will ultimately result in reboot requirement. Like "I want to install, but I can't afford a reboot, and I need to be able to run the software normally". The need for reboot indicates that there's no guarantee that you would be able to use LO normally before the reboot (although *usually* you can); so this is an important decisions to take in some cases, *before* the actual action is performed.