Created attachment 106457 [details] pop-up I got when putting a Heading Style on a title in my writer document When editing in writer I put a Style Heading 2 and then I got a pop-up window containing the following : release() on empty container
Hello Vincent, Thank you for filing the bug. Does this happen with any document you create or just that particular one? Have you tried this on a stable release like 4.3.1.2 or 4.3.2.2?
Hello Jay, Thanks for asking. I had mainly the problem with 4.3.1.2 but it seems to me that it occurs less with 4.3.2.2. I have it only on 1 document. I don't know exactly how to reproduce it. It is often when I apply a Style (Heading 3) to a line of text, then the pop-up shows and LibreOffice crashes.
Hello Jay, It seems to occur just with a particular document and it happens with release 4.3.2.2 of LibreOffice.
Hi Vincent, Can you add the file that this is happening in, so that we can investigate the problem. You can do so by visiting < https://bugs.freedesktop.org/attachment.cgi?bugid=84015&action=enter >.
Created attachment 107148 [details] Document emptied of its content This is the document emptied of its content (as it is confidential). I couldn't reproduce it in this emptied document. Sorry.
Hi Vincent, Is it possible for you to share it with us confidentially by email. It would only be shown to me to confirm the bug and to a developer who would fix the bug.
I'm very sorry, I prefer not. I hope you understand.
Hi Vincent, Unfortunately, if it is something that we cant reproduce, then its something that we wouldnt be able to fix. See if your okay with removing the confidential information using the instructions at < https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F > and if so, we can proceed with trying to fix it.
It happened to me today. I am willing to share my document with you confidentially.
Hi Iain, There is a means of scrambling up the english in a document, so that it can be submitted publicly. Please read the instructions at ( https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission#Writer_2 ) to see if this works for you and then you can submit that document.
Created attachment 111234 [details] A document that invoked this bug, recovered and redacted I had just pressed enter after typing the text of a new subheading (I think 3.5) when I saw the message that crashed LibreOffice. LibreOffice was able to recover the document but the new subheading was gone. I have attached a redacted version of the recovered copy. There seems to be no simple way to edit hyperlinks in bulk, so I didn't bother to redact those. The error hasn't appeared again yet.
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 INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/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 This NEEDINFO message was generated on: 2015-10-14
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID 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 This INVALID Message was generated on: 2016-05-09