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

soffice couldn't connect at first time #68

Closed
piotrooo opened this issue Jul 19, 2012 · 4 comments
Closed

soffice couldn't connect at first time #68

piotrooo opened this issue Jul 19, 2012 · 4 comments

Comments

@piotrooo
Copy link

Hello,

I have little troubles with unoconv in Debian 6.0. When I first time after reboot try execute command I recived:

Verbosity set to level 2
Existing listener not found.
Connector : couldn't connect to socket (Success) Trying to launch our own listener using soffice.bin.
Launch of soffice.bin failed.
Connector : couldn't connect to socket (Success) Trying to launch our own listener using soffice.
Launch of soffice failed.
Connector : couldn't connect to socket (Success) Error: Unable to connect or start own listener. Aborting.
Taking down OpenOffice with pid 1410. Waiting for OpenOffice with pid 1410 to disappear.

I execute this command from bash script:

!/bin/bash

if [ -z "$1" ]; then
echo "No match file";
exit 10;
fi

CMD=/usr/bin/unoconv -vvvvvvvvvvvv -f pdf $1.odt 2>&1

if [ $? != 0 ]; then
echo "Error generating"
echo $CMD
exit 17;
fi

exit $?;

To get verbose messages I must kill soffice process, and after this I get verbose message, end exit code.

I think something isn't correctly with soffice listener which is calling from unoconv.

This script is calling from php by exec() function.

@dagwieers
Copy link
Member

unoconv version ?

Did you try with the latest master branch ?

@ghost ghost assigned dagwieers Jul 19, 2012
@piotrooo
Copy link
Author

I'm using unoconv 0.3-6 version.

@dagwieers
Copy link
Member

That version was released in 31/08/2007, I am not interested to spend time on issues that might have been fixed already since.

@dagwieers
Copy link
Member

No feedback ?

Then I am closing this ticket, if your issue is not resolved by using the master branch, feel free to reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants