I have an appication in which I fill the OpenOffice text document using bookmarks and then save them as PDF (C#, .NET 4.0, VS 2010). The problem is that when the document filled first time then everything works fine but after closing the document using API and open new document and try to fill ( Automatically using Uno API) then Uno API process won't get response from LibreOffice. Mean second time LibreOffice process won't response on writng bookmarks and my application process wait for the response of LibreOffice. This results in hang in my application, as my process wait indefinitely response from Uno API (and may be Uno API wait for response from running LibreOffice process). The file is loaded from a template and bookmarks are filled. Program is started using soffice -accept=pipe,name=myPipeName;urp;StarOffice.ServiceManager -nodefault -nologo -nofirststartwizard -norestore using UnoUrlResolver I have connected to running office instance. It is may be some bug in Uno API thread or what can be the reason?
I have an appication in which I fill the OpenOffice text document using bookmarks and then save them as PDF (C#, .NET 4.0, VS 2010). The problem is that when the document filled first time then everything works fine but after closing the document using API and open new document and try to fill ( Automatically using Uno API) then Uno API process won't get response from LibreOffice. Mean second time LibreOffice process won't response on writng bookmarks and my application process wait for the response of LibreOffice. This results in hang in my application, as my process wait indefinitely response from Uno API (and may be Uno API wait for response from running LibreOffice process). The file is loaded from a template and bookmarks are filled. Program is started using soffice -accept=pipe,name=myPipeName;urp;StarOffice.ServiceManager -nodefault -nologo -nofirststartwizard -norestore using UnoUrlResolver I have connected to running office instance. It is may be some bug in Uno API thread or what can be the reason? As in Apache OpenOffice this bug solving procedure is written https://bz.apache.org/ooo/show_bug.cgi?id=32051 using "Negotiate=0,ForceSynchronous=1". I have tested my code with Apache OpenOffice program and there was no problem. But with LibreOffice I have started the process by including these two parameters but still it hang.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
This bug was never confirmed by a person different than the reporter. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180129
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180302