Bug 69031 - Can not open the document
Summary: Can not open the document
Status: RESOLVED DUPLICATE of bug 67699
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: x86 (IA32) Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-06 12:19 UTC by olafbond
Modified: 2013-11-21 21:02 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
sample document (7.20 KB, text/html)
2013-09-06 12:19 UTC, olafbond 		Details
console logs (3.97 KB, text/plain)
2013-09-07 06:10 UTC, Julien Nabet 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description olafbond 2013-09-06 12:19:06 UTC 
Created attachment 85326 [details]
sample document

Writer can not open the included document.
Input/Output error.
Comment 1 Julien Nabet 2013-09-07 06:10:29 UTC 
Created attachment 85388 [details]
console logs

On pc Debian x86-64 with master sources updated yesterday or with 4.1 sources updated 1 week ago + brand new LO profile in both cases, I could open the file.

However, I noticed some problem logs so I attached them.
Comment 2 Julien Nabet 2013-09-07 06:12:09 UTC 
olafbond: for the test, could you give a try to 4.1.1, rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and tell if you still reproduce this?
Comment 3 olafbond 2013-09-18 13:25:49 UTC 
4.1.1.2 Can't open still
"rename your LO directory profile" - do not understand what is it.
Comment 4 Julien Nabet 2013-09-18 13:28:26 UTC 
olafbond: rename your Libreoffice directory profile, ie:
    Before Vista: \Documents and Setting\<user name>\Application Data\libreoffice\4\user   (LibreOffice 4)
    From Vista: %appdata%\libreoffice\4\user   (LibreOffice 4)
Comment 5 Maxim Monastirsky 2013-09-22 14:55:43 UTC 
It's HTML with doc suffix, so a dup of Bug 67699.

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