Description:
I am trying to add functionality to convert .DOCX files to .PDF in a web app I'm developing. The app is using Node.js, which is on an AWS EC2 instance (using Elastic Beanstalk) running Amazon Linux AMI (release 2018.03). I'm using the office-to-pdf package (https://www.npmjs.com/package/office-to-pdf) which is really just running `soffice --headless --convert-to pdf somefile.docx` under the hood.

I installed LibreOffice 6.0.7.3 and all dependencies and was able to run the headless conversion just fine while SSH'd in as 'ec2-user'. No problem. But the programmatic call in office-to-pdf hangs every time. I found that it runs as a different user, 'nodejs', and when I do `top -u nodejs` I can indeed see the soffice.bin and oosplash processes, but they are sleeping. When I kill them, I get the message:

javaldx failed!
Warning: failed to read path from javaldx

This is not just the package; I can do `sudo -u nodejs soffice --headless --convert-to pdf somefile.docx` and it shows the same exact message and hangs the process.

I have read some bug reports on here and some questions on Super User that pointed to the .config directory -- I tried opening the permissions up with `chmod -R 777 .config/` to no avail. I also tried changing the owner & group from the default user 'ec2-user' to 'nodejs' to no avail.

This may ultimately be a Linux question but I could not find any info on javaldx to try to dive deeper.

Steps to Reproduce:
1. Launch AWS Elastic Beanstalk Node.js environment with Amazon Linux AMI release 2018.03. (Also set up SSH)
2. SSH into instance.
3. Install LibreOffice 6.0.7.3 release typically.
4. Try to run `soffice --headless --convert-to pdf somefile.docx` with some sample file. Observe that it converts successfully.
5. Try to run `sudo -u nodejs soffice --headless --convert-to pdf somefile.docx` to generate the warning message/hang.


Actual Results:
The conversion process hangs forever, therefore failing.

Expected Results:
The command is expected to convert the file regardless of the user calling it.


Reproducible: Always


User Profile Reset: No



Additional Info:
I have not and can not run the LO GUI. I only have access to the CLI.