Bug 69230 - FILEOPEN: particular DOCX file refuses to open with repair/general error messages
Summary: FILEOPEN: particular DOCX file refuses to open with repair/general error mess...
Status: RESOLVED DUPLICATE of bug 64395
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: filters and storage (show other bugs)
Version:
(earliest affected)
4.1.1.2 release
Hardware: All All
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-11 15:44 UTC by Dave Richards
Modified: 2014-08-07 06:17 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Offending File (20.55 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2013-09-11 15:44 UTC, Dave Richards
Details
pdf file to be tested (366.97 KB, application/pdf)
2014-01-23 08:13 UTC, Kevin Suo
Details
docx file converted in skydrive, from the pdf file. (63.62 KB, application/vnd.ms-word.document.12)
2014-01-23 08:14 UTC, Kevin Suo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Richards 2013-09-11 15:44:18 UTC
Created attachment 85643 [details]
Offending File

The attached document cannot be opened in LibreOffice, but opens fine with MS Office.  Observations are some prompts about a damaged file and an attempt to recover the file and then finally a crash with General I/O.

This isn't a case of just one bad file, we received 10 files from one of our vendors and none of them will open with the same results.

Tested in 4.2 (MASTER) and 4.1.1 and crashes identically.
Comment 1 Maxim Monastirsky 2013-09-11 16:18:00 UTC
Reproducible with LO 4.1.1.2 under Ubuntu 13.10 (64-bit). First LO claims that the file is corrupted, and suggest to repair. If I choose 'Yes' I get the following message: 'The file '$(ARG1)' could not be repaired and therefore cannot be opened.' followed by 'General Error' message.

I'm able to open the document with Word 2010 without any issues.

A 'General Error' is not a crash, so I'll edit the summary. Also raising priority since user can't open his document at all. Also changing version to oldest known.
Comment 2 Oliver 2013-10-03 15:20:43 UTC
I have got the same problem several times with docx documents first edited by a colleague using MSWord, I could open the files without problems, but after working for a while and saving regularly (autosave off because of the bug with the images), and closing, I was not able to re-open them and get a "Erreur générale. Erreur d'entrée/sortie générale." In French, which roughly translates to "General Error. General input/output error". 
I have only had this since the last update to version 4.1.1.2
This is a BIG problem
Comment 3 Kevin Suo 2014-01-23 08:13:24 UTC
Created attachment 92642 [details]
pdf file to be tested

I encountered the same problem when I converted the attached pdf file to docx in Skydrive.

As the pdf-to-docx function in skydrive is very relevent to MS Office 2013, so the problem I encountered must be the same as discussed in Comment #1.

Steps:
1. convert the pdf file to docx in skydrive; 
2. download and open with LO 4.1.4.2, says "is corrupt and therefore cannot be opened"; when try to repair, says "The file '$(ARG1)' could not be repaired and therefore cannot be opened.".
3. Open with LO 4.2.0.3, just says "General Error. General input/output error."
3. open with MSO or other office suites (i.e., WPS), opens OK.
Comment 4 Kevin Suo 2014-01-23 08:14:32 UTC
Created attachment 92643 [details]
docx file converted in skydrive, from the pdf file.
Comment 5 Maxim Monastirsky 2014-01-23 11:24:37 UTC
'Critical' is only suitable for crashes, see https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Comment 6 Gerhard Schaber 2014-07-02 08:45:00 UTC
I also have the same problems with PDF files converted to RTF format using PDF Expert, and with several Word documents. OpenOffice does not have this issue.
Comment 7 Maxim Monastirsky 2014-08-07 06:17:34 UTC
Same issue with backslash as in Bug 64395.

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