Bug 39084 - LibO systematically aborts when opening specific .doc files
Summary: LibO systematically aborts when opening specific .doc files
Status: RESOLVED DUPLICATE of bug 38623
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.4.1 release
Hardware: Other Windows (All)
: medium normal
Assignee: Caolán McNamara
Depends on:
Reported: 2011-07-09 02:58 UTC by Helmut Leininger
Modified: 2011-07-09 08:31 UTC (History)
0 users

See Also:
Crash report or crash signature:

contains the document and thje lock file (4.48 KB, application/zip)
2011-07-09 02:58 UTC, Helmut Leininger
extract the .doc itself (28.50 KB, application/msword)
2011-07-09 07:33 UTC, Caolán McNamara

Note You need to log in before you can comment on or make changes to this bug.
Description Helmut Leininger 2011-07-09 02:58:21 UTC
Created attachment 48914 [details]
contains the document and thje lock file

LibreOffice always aborts when trying to open the attached .doc file with a message about "Folgende Dokumente werden wieder hergestellt", but the list of files in it is empty.

When you try again, the Recovery window opens with an empty list.

It may be, you can open and close other documents, but sometimes the processes soffice.exe and soffice.bin are multiplicated. I hace already seen more than 3 pairs of it. In this case, LibO will just ignore every attempt to apen any document (from users visibility) and add another process pair.

The only way out seems to be to
1) kill the processes
2) delete the lock file(s)

This happens both in WindowsXP and Windows7
Comment 1 Caolán McNamara 2011-07-09 07:33:40 UTC
Created attachment 48916 [details]
extract the .doc itself

extract and reattaching the .doc itself so it'll be picked up by the attachment scanners as a sample .doc
Comment 2 Caolán McNamara 2011-07-09 07:43:13 UTC
Crash under Linux 3.4.1 alright, none in master however, so looks like this has been fixed in the interim.
Comment 3 Caolán McNamara 2011-07-09 08:31:11 UTC

*** This bug has been marked as a duplicate of bug 38623 ***