Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unoconv needs 2 times to connect to LibreOffice #7

Closed
wursti opened this issue Jul 10, 2011 · 5 comments
Closed

unoconv needs 2 times to connect to LibreOffice #7

wursti opened this issue Jul 10, 2011 · 5 comments
Labels
Milestone

Comments

@wursti
Copy link

wursti commented Jul 10, 2011

on my machine unoconv needs everytime 2 times to connect to libreoffice.
first time it says:
Error: Unable to connect or start own listener. Aborting.
on second time it is working.
i havo no idea why it doesn't work. it doesn't matter if libreoffice is running or not.

@dagwieers
Copy link
Member

Yes, I have noticed that recently as well, have you tried using the -T/--timeout option to see if increasing the timeout helps ?

I am going to revise the code that takes care of spawning openoffice/libreoffice to see what can be improved. One uncommitted change allows to try swapping the python interpreter if this is needed for the pyuno library. But it needs a lot more testing :-/

@dagwieers
Copy link
Member

Can you please try the current HEAD ? It has some improvements to how it loads and starts OpenOffice/LibreOffice, and together with LibreOffice 3.4.3 it works more reliable and feels faster.

@rdlugosz
Copy link

rdlugosz commented Jan 7, 2012

FWIW I was seeing a similar problem and also one where unoconv would segfault and thus leave an soffice.bin process running. Using HEAD made both issues go away; I had been using the 0.4 release prior to today.

Thx for a useful script!

@dagwieers
Copy link
Member

Thank you for the feedback. Maybe it is time to release 0.5 anyway ?

@dagwieers
Copy link
Member

I am closing this issue because I believe this is fixed, if you still have an issue please reopen this issue !

@dagwieers dagwieers added the bug label Jul 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants