-
Notifications
You must be signed in to change notification settings - Fork 376
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: UnoException during export phase #66
Comments
Oh I'm also on Centos OS |
Same thing on RHEL6 when converting from pdf: unoconv -f docx 123.pdf |
Hmm, I am interested to have one of these files. Are you using the latest 0.5 release ? Or maybe the master branch ? It is really necessary for me to know what version you are using. |
I have the exact same issue, only with docx or docx7 (conversion to doc or pdf works fine).
Original file is here: http://cdn.lexpressproperty.com/images/93fb4ddea91d405740f6b57bcf8d4d4f.odt. |
Works fine for me using the default RHEL6 LibreOffice:
Or using the upstream LibreOffice packages:
Please use a recent LibreOffice and take the unoconv master branch for testing. We are preparing a v0.6 release that fixes most of the known issues. |
BTW To test the latest master branch, you can simply clone the Git repository and run the unoconv script directly from the tree. There is no need to install a package or copy binaries/libraries. If you're done testing, you can remove the Git tree from the system and everything is as it was before. And you don't need root-access either. |
I am closing this issue because we lack information to troubleshoot this. We cannot reproduce it and suspect either that unoconv is an older release, or instead the environment (LibreOffice, OpenOffice, OS, configuration) is different. Without more information it is hard to tell. Please reopen if you can still reproduce and interested in troubleshooting... |
I was able to recreate the above symptom while converting doc, xls, and ppt documents with the command 'sudo /usr/bin/unoconv -f txt -o I determined that my problem was the result of the listener not having write permission to the target location. The listener, as I came to discover, was started as me rather than root. When I killed the listener and ran unoconv without one I had no problem. Also when I started the listener as root I was perfectly able to write the output file. I dont assert that this ticket should be reopened, but since my initial searching bought me here I thought this update may be useful to others. Also, in the event that this is of any use to you: $ unoconv -V platform posix/linux2 $ uname -a |
I had the same problem, turns out that I had a LibreOffice Writer document open. |
Just fyi: I'm seeing this problem on CentOS 6 with unoconv 0.6-8 (recompiled package from Fedora) and LibreOffice 4.0. The problem disappears when I'm not using '--stdout'. Also the problem does not happen on Fedora 20 with LibreOffice 4.2. As the unoconv source code is exactly the same on both systems I assume this is a LibreOffice problem which was fixed in 4.1 or 4.2. |
When I try to convert anything to swf I get this god awful error message:
unoconv: UnoException during export phase: Unable to store document to file:///buildblob/shonuff.swf with properties ((com.sun.star.beans.PropertyValue){ Name = (string)"FilterName", Handle = (long)0x0, Value = (any){ (string)"draw_flash_Export" }, State = (com.sun.star.beans.PropertyState)DIRECT_VALUE }, (com.sun.star.beans.PropertyValue){ Name = (string)"OutputStream", Handle = (long)0x0, Value = (any){ (com.sun.star.uno.XInterface)0x1bbd4d68{, supportedInterfaces={com.sun.star.lang.XTypeProvider,com.sun.star.io.XOutputStream}} }, State = (com.sun.star.beans.PropertyState)DIRECT_VALUE }, (com.sun.star.beans.PropertyValue){ Name = (string)"FilterData", Handle = (long)0x0, Value = (any){ ([]any){} }, State = (com.sun.star.beans.PropertyState)DIRECT_VALUE }, (com.sun.star.beans.PropertyValue){ Name = (string)"Overwrite", Handle = (long)0x0, Value = (any){ (boolean)true }, State = (com.sun.star.beans.PropertyState)DIRECT_VALUE }). Exception:
I have no idea what I did wrong. Any suggestions on how to get this to work? I have the following of open office installed:
openoffice.org-core.x86_64
openoffice.org-headless.x86_64
openoffice.org-pyuno.x86_64
openoffice.org-sdk.x86_64
openoffice.org-writer.x86_64
Am I missing anything?
The text was updated successfully, but these errors were encountered: