Bug 84440 - DOCX Crash on opening document, corrupt comment
Summary: DOCX Crash on opening document, corrupt comment
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 4.3.1.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-29 00:04 UTC by mycae
Modified: 2014-09-29 08:17 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description mycae 2014-09-29 00:04:24 UTC
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, 
Package: libreoffice-writer
Source: libreoffice
Version: 1:4.3.1-2


Thanks!
Comment 1 Robinson Tryon (qubit) 2014-09-29 02:26:38 UTC
(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).

Hiya,
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:
https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission

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:
https://www.libreoffice.org/download/
http://dev-builds.libreoffice.org/daily/master/

After you test out the document with the latest builds, please change the bug status back to 'UNCONFIRMED'.

Thanks!
Comment 2 mycae 2014-09-29 08:17:50 UTC
Hi,

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!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.