Description: Under Tools -> Options -> LibreOffice -> Advanced, I disable Java. I get the following message on opening any Impress file: LibreOffice requires a Java runtime environment (JRE) to perform this task. However, use of a JRE has been disabled. Do you want to enable the use of a JRE now? In order to fix, I need to know what "this task" is. If it is a plugin, then I need to know what plugin. The error message does not give me information that I need to resolve the problem. Impress appears to run OK in spite of the error, but it is annoying. The error box does not occur if I start in safe mode. However, it would still be nice to get the error message improved. Steps to Reproduce: 1. Disable Java 2. ooffice foo.odp 3. Actual Results: LibreOffice requires a Java runtime environment (JRE) to perform this task. However, use of a JRE has been disabled. Do you want to enable the use of a JRE now? Expected Results: An error message that gives me the information I need to disable/remove whatever is trying to use Java. Reproducible: Always User Profile Reset: Yes Additional Info: libreoffice-6.2.3.2-4.2.x86_64 libreoffice-base-6.2.3.2-4.2.x86_64 libreoffice-base-drivers-firebird-6.2.3.2-4.2.x86_64 libreoffice-branding-upstream-6.2.3.2-4.2.noarch libreoffice-calc-6.2.3.2-4.2.x86_64 libreoffice-draw-6.2.3.2-4.2.x86_64 libreoffice-filters-optional-6.2.3.2-4.2.x86_64 libreoffice-icon-themes-6.2.3.2-4.2.noarch libreoffice-impress-6.2.3.2-4.2.x86_64 libreoffice-l10n-en-6.2.3.2-4.2.noarch libreoffice-mailmerge-6.2.3.2-4.2.x86_64 libreoffice-math-6.2.3.2-4.2.x86_64 libreoffice-pyuno-6.2.3.2-4.2.x86_64 libreoffice-qt5-6.2.3.2-4.2.x86_64 libreoffice-share-linker-1-4.6.noarch libreoffice-writer-6.2.3.2-4.2.x86_64 Linux Socrates 5.1.4-1-default #1 SMP Wed May 22 11:11:40 UTC 2019 (0739fa4) x86_64 x86_64 x86_64 GNU/Linux CPE_NAME="cpe:/o:opensuse:tumbleweed:20190529" OpenGL is not enabled.
I notice that the Whiteboard was changed to "QA:needsComment". Is this a comment you need from me?
@Kenneth : no, the needscomment is for a QAer to respond. Does your question relate to the clarity of the message (or lack thereof), or the underlying problem of having deactivated Java ? By default, LO doesn't come with any Java extensions to my knowledge (I'm prepared to stand corrected) that are activated when using Impress. The only other one I can think of is the optional LanguageTool extension. I imagine that there might be some drawing tool extensions written in Java too, but these are not generally installed by default, unless your distribution has decided to do so. It sounds to me like this is more of a distrib packaging problem with the version of LO you have installed ? I notice in your description of the bug you use 'ooffice' as the command to launch LO, yet official TDF versions of LO use 'soffice' - again, is this distrib-specific ? I would be hesitant to mark this as one of our bugs without further information.
The reasoning is that if you have installed a Java extension, then you willingly deactivate Java within LO, it should be no surprise to have an error message. Granted, the message could possibly be more helpful in pointing out which extension requires Java, but if you, the user, or the admin, has already installed such an extension, then they should know that already, ergo, identification is relatively easy ?
Hmm, maybe the optional filters package is the one causing the problem, what does that provide ?
Checking out those package contents and comments, I see : 2019-02-06 - Gustavo Yokoyama Ribeiro <gyribeiro@suse.com> - Fixed bug #1124285 - Add patch to build with java-11.2: * java112.patch Seems to me that that filter package is indeed the cause of the message.
(In reply to Alex Thurgood from comment #2) > Does your question relate to the clarity of the message (or lack thereof), > or the underlying problem of having deactivated Java ? My comment is about the message and not about Java itself. The message does not give me the information I need to resolve the problem. It says that something does not work, but not what is not working. It's kind of like the "Bad file" error message. It does not tell me what was wrong or what it was trying to do, so I cannot fix the error. > By default, LO doesn't come with any Java extensions to my knowledge (I'm > prepared to stand corrected) that are activated when using Impress. > > The only other one I can think of is the optional LanguageTool extension. I > imagine that there might be some drawing tool extensions written in Java > too, but these are not generally installed by default, unless your > distribution has decided to do so. I checked an I do have LanguageTool installed, probably as a part of the default install for Tumbleweed. I disabled it, disabled Java, and the error went away. So this is the tool causing the error. Now, the error message needs to tell me this. I would not have found this without your mentioning it. > It sounds to me like this is more of a distrib packaging problem with the > version of LO you have installed ? The generation of the error message is an issue with LO (or the extension). > I notice in your description of the bug you use 'ooffice' as the command to > launch LO, yet official TDF versions of LO use 'soffice' - again, is this > distrib-specific ? ooffice is a shell script that runs soffice. Years ago I got in the habit of typing ooffice. That never stopped working, so my fingers keep doing it. Does what I have found here mean that this needs to be a bug for LanguageTool? What is generating the error message?
[Automated Action] NeedInfo-To-Unconfirmed
Unfortunately, the point is, that you, your systems administrator, or whoever setup the machine, or the OS due to its particular way of handling dependencies, installed a Java extension that spell checks for each module of the suite. It is therefore not really a surprise when the user deactivates Java and gets a whiney message from LO saying that something is wrong, but that is just my personal opinion. It is hardly LO's fault that soemthing or someone installed the extension in the first place. How is LO supposed to know what a package maintainer might decide to "add-on" to LO (and possibly not tell the user) and then be expected to be responsible for it ? I'm going to confirm this request for enhancement, and change the title to better reflect the idea behind the request, but as I have no idea of the kind of development required, I have no idea whether it will/can even be implemented.