Description of problem: Since the latest F16 update to libreoffice, you can no longer programatically control things through the com.sun.star.comp.helper.Bootstrap class in /usr/lib64/libreoffice/ure/share/java/juh.jar The problem seems to be that Bootstrap includes a number of command-line options to ooffice, which produce the following series of warnings and one error: CE> Warning: -nologo is deprecated. Use --nologo instead. CE> Warning: -nodefault is deprecated. Use --nodefault instead. CE> Warning: -norestore is deprecated. Use --norestore instead. CE> Warning: -nolockcheck is deprecated. Use --nolockcheck instead. CE> Warning: -accept=pipe,name=uno4377571654706408244;urp; is deprecated. Use --accept=pipe,name=uno4377571654706408244;urp; instead. CO> Unknown option -nocrashreport CO> Run 'soffice --help' to see a full list of available command line options. After the "Unknown option -nocrashreport", ooffice exits without setting up the connection. This definitely works with libreoffice-3.4.3.2-11, and I suspect it probably even worked with some of the earlier 3.4.5-* versions (can't test though). Version-Release number of selected component (if applicable): libreoffice-3.4.5.2-8.fc16.src.rpm How reproducible: Every time Steps to Reproduce: 1. Run the attached Java program (with ooffice running or not) Actual results: Error messages as above, and program hangs indefinitely Expected results: Connection established Additional info:
Created attachment 573071 [details] Java test program to trigger the bug
hmm, nocrashreport needs to be added to the known options I guess
Will be fixed in >= libreoffice-3.4.5.2-10.fc16 You can drop nocrashreport from your code FWIW in the meantime it doesn't do anything anyway as the crash reporter isn't built (we just rely on abrt)
Thanks for the extremely quick response! Just to note, though, "-nocrashreport" isn't in my code; it's automatically added if you do Bootstrap.bootstrap() (using the jar file provided with LibreOffice) and you can't edit the command line options.
(In reply to comment #4) > Just to note, though, "-nocrashreport" isn't in my code; it's automatically > added if you do Bootstrap.bootstrap() (using the jar file provided with > LibreOffice) and you can't edit the command line options. Yes. And within LibreOffice, --nocrashreport is handled directly down in sal/osl/{unx/signal.c,w32/signal.cxx}, so <http://cgit.freedesktop.org/libreoffice/core/commit/?id=4efbd87e31e7488dfcdd1d07ff979f1f59b8b1f1> "Resolves: rhbz#800272 complain about unknown command-line options" should -- non-obviously -- not have complained about it.
libreoffice-3.4.5.2-10.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/libreoffice-3.4.5.2-10.fc16
Package libreoffice-3.4.5.2-10.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreoffice-3.4.5.2-10.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-5070/libreoffice-3.4.5.2-10.fc16 then log in and leave karma (feedback).
libreoffice-3.4.5.2-10.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.