Steps to reproduce:
 Start LibreOffice and install extension Language Tool.
 Enable use of Java Runtime Environment: Tools > Options... > LibreOffice > Advanced > disable Java, then OK
 Close LibreOffice.
 Start LibreOffice again. The message „LibreOffice requires a Java runtime environment ...“ is displayed. At this point a more specific message would be fine: e. g. „The extension Language Tool requires a Java ...“. Go on with steps [5a] or [5b] or [5c]
[5a] Click “Yes“. The message „Due to an unexpected error, LibreOffice crashed. ...“ is displayed. Expected: Start of LibreOffice with JRE enabled.
[6a] Click ”OK“ and wait. Now LibreOffice starts correctly.
[5b] Click “No“. The message „Due to an unexpected error, LibreOffice crashed...“ is displayed. Expected: Start of LibreOffice with JRE disabled.
[6b] Click ”OK“ and wait. LibreOffice starts again with message of step .
[5c] Click ”Cancel“. The message „Due to an unexpected error, LibreOffice crashed. ...“ is displayed. From my point of view a Cancel button does not make sense here. Either it should be greyed or a Cancel button should not be displayed.
If you deinstall Java completely instead of only disable Java in LibreOffice you will get a never ending story. In this case you have to close LibreOffice with the Task Manager.
I checked this bug only with the extension „Language Tool“. Hence it is not sure if this problem also occurs with other extensions which need Java.
Bug also exists in Version 4.0.4. Bug does not exist in Version 3.6.7, hence regression.
Operating System: Windows 7
Version: 220.127.116.11 rc
Last worked in: 18.104.22.168 rc
Confirmed under Windows XP Pro x86 SP3 en_US using LO 22.214.171.124 and 4.2 Beta2
LibreOffice should NOT crash because of a misbehaved extension.
can't get a crash on Linux...
Stephan can you take a look?
It seems to be fixed in LO 126.96.36.199. I can reproduce the crash in 4.2/4.1/4.0 series, but not in 4.3.
I can confirm Andras: Bug exists in version 4.2.4 but not in 4.3.0. Also checked version 188.8.131.52. Also this version works for me. Hence Bug closed.
Migrating Whiteboard tags to Keywords: (notBibisectable)