Problem connecting JabRef to OpenOffice 4.1.15

Help
1

Have been using JabRef with OpenOffice and LibreOffice for years, but had to update OS etc… Currently using OpenOffice 4.1.15, OpenJDK 11.0.24, and JabRef 3.8.2 under Linux Mint 21.3. Path autodetection fails. Manual connection allows entry of correct paths into the appropriate fields of the “Set Connection Parameters” panel (/opt/openoffice4/program/soffice and /opt/openoffice4/program/classes), but clicking on the panel’s OK button generates this error msg: Could not connect to running OpenOffice/LibreOffice. File not found: /opt/openoffice4/program/classes/unoil.jar/program/classes/unoil.jar
Note the weird partial duplication in that error msg. Is the problem with OOO or Java, and is there a workaround? (Why don’t I just switch to LO? Unfortunately I have to use OOO for many tasks that involve using EPS image files, and LO lost the ability to properly handle EPS almost 10 years ago.)

2

I suppose you have to manually find the directory libreoffice is installed in your operating system.

If nothing else helps, you could try to manually download and insert the dependencies in that folder path: Download unoil.jar - @org.openoffice. Maybe you find something, if you sift through the documentation of OpenOffice as well: API/Tutorials/Java - Apache OpenOffice Wiki

3

Maybe How to find the installation path for a software under linux? - Unix & Linux Stack Exchange is a good starting point.

4

Maybe my initial post was too long, or not sufficiently explicit.

“Path autodetection fails. Manual connection allows entry of correct paths into the appropriate fields of the “Set Connection Parameters” panel (/opt/openoffice4/program/soffice and /opt/openoffice4/program/classes), but clicking on the panel’s OK button generates this error msg: Could not connect to running OpenOffice/LibreOffice. File not found: /opt/openoffice4/program/classes/unoil.jar/program/classes/unoil.jar”

But thanks for the replies. Any other ideas? Like, is there a config file that I can edit, instead of fooling around with the (apparently confused/broken) GUI-based way to specify paths?