Dear Libreoffice team,
I have a document which contains track-changes comments. When opening the document libreoffice exits immediately. GDB shows no stack when running writer and opening the document.
This happens every time and only for this document. Word is able to, after a complaint "one or more comments referenced in this document are missing or corrupt", recover the document contents and continue. The document was saved from libreoffice, in docx format, after initially being created in windows by a different author. Previous load/save cycles have been OK.
Unfortunately I cannot provide the document publicly, however I can provide it in-confidence to a dev, for testing purposes (eg for minimisation, the original document would need to be deleted). If this is not acceptable, please close this bug.
I am using debian-testing,
(In reply to comment #0)
> Dear Libreoffice team,
> I have a document which contains track-changes comments. When opening the
> document libreoffice exits immediately. GDB shows no stack when running
> writer and opening the document.
> Unfortunately I cannot provide the document publicly, however I can provide
> it in-confidence to a dev, for testing purposes (eg for minimisation, the
> original document would need to be deleted).
We might be able to find a dev to take a look at your document privately, but before we go down that path, maybe you could sanitize the data in it:
If the bug is triggered by something specific in the tracked changes, then that might not be workable, but I think it's worth consideration.
> I am using debian-testing,
> Package: libreoffice-writer
> Source: libreoffice
> Version: 1:4.3.1-2
A couple more quick things for you to try:
- Try to repro the problem on the 4.3.2 release as well as a daily build of the master branch, and let us know the results:
After you test out the document with the latest builds, please change the bug status back to 'UNCONFIRMED'.
Thanks for the quick response. Minimisation/sanitation using libreoffice is unfortunately not an option (as per your link), as libreoffice crashes when loading the document. Those steps all suggest using libreoffice in some way, which is not possible.
Its not clear to me what those daily build debs are against, so to do a check against a newer version I would need to compile from source (debian does not guarantee binary compat in any way), which could (once started) take a day or two. I might investigate this if I find the time, but I admit it is not massively likely.
Give me a week and we will see how I get on!
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:
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!
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
-- The LibreOffice QA Team
This INVALID Message was generated on: 2015-05-06