Created attachment 193030 [details]
crash-info.txt: backtraces with windbg and gdb

I found my LibreOffice installation crashing after my company
rolled out a centralized silent upgrade to 24.2.0.3.
This happened most probably while I had an instance
of LibreOffice and Firefox running.


Now starting from a cmd like this:
  cd "C:\Program Files\LibreOffice\program"
  soffice.com

Following is shown:
The application cannot be started.
The component manager is not available.
("file:///C:/Program%20Files/LibreOffice/program/types.rdb: no such file at C:/cygwin64/home/buildslave/source/libo-core/cppuhelper/source/typemanager.cxx:2070")


This happened also after renaming the %APPDATA%\libreoffice folder.

And this might be similar to what bug #123012 describes.



I saved the "C:\Program Files\LibreOffice" folder and did a Repair installation
with the LibreOffice_24.2.0_Win_x86-64.msi file in C:\Windows\Installer.
(Unfortunately windows decided to rename it to fe5b6.msi.)

During the Repair installation it asked to close Firefox.
And later asked for the location of LibreOffice_24.2.0_Win_x86-64.msi again.

Afterwards the installation was working fine again.


A comparison of the saved "C:\Program Files\LibreOffice" and the now working
one shows following differences:

These files are after repair existing, but did not before:
C:\Program Files\LibreOffice\program\types.rdb
C:\Program Files\LibreOffice\program\types\oovbaapi.rdb
C:\Program Files\LibreOffice\program\types\oovbaapi.rdb
C:\Program Files\LibreOffice\share\config\images_colibre.zip

Different, no error found inside both:
C:\Program Files\LibreOffice\program\logs\maintenanceservice-install.log



From my point of view it would be a better user experience if
the missing types.rdb could be warned about with a dialog message,
maybe with the hint to do a repair install.
And maybe avoiding the crash completely and just exit.