Reputation: 4740
I am trying to convert docx to pdf using unoconv
, but getting Error: Unable to connect or start own listener. Aborting.
when I run unoconv -f pdf 1234.docx
.
So, there must be some listener. I then started the listener via unoconv --listener
.
I tried ps aux | grep soffice
, and found soffice.bin.
So I tried unoconv -f pdf 1234.docx
again. It still gave me the same error: Error: Unable to connect or start own listener. Aborting.
What am I doing wrong here?
Upvotes: 20
Views: 16468
Reputation: 31
You need to kill all soffice.bin
processes before executing unoconv
Upvotes: 3
Reputation: 23798
Failing to start instance hints at the inability of the script to find the LibreOffice program.
Do this basic test:
Copy the unoconverter to "libreoffice/program" folder.
IMPORTANT: Go there and try to execute ./soffice
to verify that the soffice runs itself.
Now run unoconv with the version of python that shipped with the LibreOffice by typing ./python unocov -f pdf 1234.docx
You should see the converted file in the same directory now. Kill the soffice process and retry if it generates the same error.
Upvotes: 0
Reputation: 1
It fails with the error in the question if it does not find the LibreOffice personal configuration file, but it also creates them before exiting. The second run succeeds.
You can reproduce the error but removing the personal configuration files, then trying to run unoconv:
$ rm -rf .config/libreoffice/
$ unoconv foo
Error: Unable to connect or start own listener. Aborting.
https://github.com/dagwieers/unoconv/issues/241
Upvotes: 0
Reputation: 404
unoconv does not support .docx / .pptx etc.
You need to use the old document extension, which is .doc, .ppt.
A simple rename would probably solve the problem.
Upvotes: -8
Reputation: 622
You have to kill all the soffice.bin processes before trying to use unoconv. I didn't have to do any "unoconv --listener" command.
Upvotes: 11