I first installed LO 5.0.5.2 x64, then upgraded to 5.1.3.2 x86 version. Everything went fine, but the old files remained in C:\Program Files\LibreOffice 5 after the upgrade (the new files were installed in C:\Program Files (x86)\LibreOffice 5 as expected).
Of course they remain, the "upgrade" you performed is a new complete installation into a different location. For the time being until an incremental update mechanism is implemented bug 54242 (and related) the Windows installer is full install package. If you'd wanted to "upgrade" in place you needed to select the 64-bit installer for download, and even then "all" it would do is overwrite the existing DLLs. If there is an issue, it would be that the "update" notification sends you to the download page, but does not adjust the landing location for the 32-bit/64-bit instance and localization already in place.
I consider it an issue that now there's an orphaned LibreOffice in the system that has no shortcuts, no uninstall function (what was there is taken over by the new version's), and the only option to get rid of it is manual deletion. I'd expect the installer to first uninstall the old version, and then install the new one. Note that it happens correctly, with no leftover files, in a 32-bit -> 64-bit upgrade, but not vice versa.
Sure, we can call it an enhancement. @Andras, any thoughts on a custom action in the MSI installer for checking existence of both 64-bit as well as 32-bit installations when installing either. Probably fine to abort the install and have the user manually remove the prior version. But not unreasonable to provide some check to prevent orphaned 32 or 64 bit installation cut off from APPWIZ.exe add/remove.
http://www.advancedinstaller.com/forums/viewtopic.php?t=30787 Aron, did it happen on Windows 7?
Yes, it's Windows 7.
Is this reproducible?
Dear Aron Budea, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Aron Budea, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp