Created attachment 148704 [details] Upgrade of types.rdb failed These are two somewhat rare situations that randomly plague our user base. * When we centrally trigger the upgrade process on Windows 7 via SCCM, and users are running LO at the same time, the upgrade sometimes - but not always; we are yet unsure exactly how to trigger this behavior - fails and leaves an inoperable installation behind. The error message is on the types-rdb-54.png picture, sent by one of our users. Some .rdb files fail to correctly upgrade and then LO no longer starts, only a reinstall helps. * Another issue is on the second picture (LO5-6.PNG), taken while testing a 5.4 -> 6.0 upgrade in the test environment while LO was running. Because the default install directory changed to be versionless, the upgrade run smoothly, but left the running process with removed libraries to a swift crash. This can be called sort of a bad user experience. We think these two issues have a common root, that is the lack of proper detection of a running instance and subsequently marking every new file - not only a select few (shown on LO607-install.PNG) - for delayed installation.
Created attachment 148705 [details] Upgrade with install dir change can cause crash
Created attachment 148706 [details] Upgrade can mark some files for later replacement, but not every single one
LibreOffice MSI installer itself does not has a custom logic to detect running instances; that isn't a subject for custom logic actually, but is a function of Windows Installer service, which has the MSI database for reference which files must be removed/replaced, and if they are currently in use by some process. If it cannot replace them, it may offer a dialog to user (in UI mode), and delay-install the locked files. In any case, if only some of files are being used by a process, those files only would be delay-installed; others would be removed/replaced, which of course would mean a crash opportunity for a running process which suddenly decided to access a file which was removed (by the way, even if there were not directory change, such an operation can give crashes, because replaced (i.e., existing) newer files could happen to be incompatible with running older executable). Of course, I agree with you that an IT department doing such replacements while users work creates sort of bad user experience ...
I also observed the issue with "types.rdb: no such File" on some Windows 7 computers during centralized upgrade LO 5.3 -> LO 5.4.7.2. I didn't see it myself before 5.4 although there was something for LO 5.1 on ASK. Similar at https://ask.libreoffice.org/en/question/138028/libreoffice-54-fatal-error/. I confirm that reinstall was needed, profile reset didn't help.
(In reply to Timur from comment #4) > I also observed the issue with "types.rdb: no such File" on some Windows 7 > computers during centralized upgrade LO 5.3 -> LO 5.4.7.2. > I didn't see it myself before 5.4 although there was something for LO 5.1 on > ASK. Similar at > https://ask.libreoffice.org/en/question/138028/libreoffice-54-fatal-error/. > I confirm that reinstall was needed, profile reset didn't help. Moving it to NEW then...
Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 160099 has been marked as a duplicate of this bug. ***
*** Bug 160055 has been marked as a duplicate of this bug. ***