Bug 65033 - FILEOPEN: Writer failure due to an unexpected error when open particular .DOC file (REGRESSION from LibO 4.0.3.3)
Summary: FILEOPEN: Writer failure due to an unexpected error when open particular .DOC...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.1.0.0.beta1
Hardware: All Windows (All)
: high major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2013-05-27 10:57 UTC by Timon
Modified: 2013-06-21 13:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
doc file that could not be opened (58.50 KB, application/msword)
2013-05-27 10:57 UTC, Timon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timon 2013-05-27 10:57:47 UTC
Created attachment 79842 [details]
doc file that could not be opened

LibreOffice Version: 4.1.0.0.beta1 Build ID: 5271b34bec742e190e2fe5a7dadb7334a705b54 on Russian Windows XP Professional SP3 (32bit)

If we try to open attached file, Writer failures due to an unexpected error. If we try to recover file, process loops (failure after each recover attempt) and file could not be open.

In LibreOffice Version: 4.0.3.3 Build ID: 0eaa50a932c8f2199a615e1eb30f7ac74279539 the same file is opened without any problems.

If there would be need, I have more 10 files with a similar problem.
Comment 1 Thomas van der Meulen [retired] 2013-05-27 14:47:26 UTC
Thank you for your bug report, I can't reproduce this bug running libreoffice Version: 4.1.0.0.beta1
Build ID: 3a2c2d2417101e45fe07cfd8358acf2204a98f3 on Mac osx 10.8.3
Comment 2 Jorendc 2013-05-27 15:01:26 UTC
Thanks!

I can reproduce this behavior using Windows 7 x64 with LibreOffice Version: 4.1.0.0.alpha1+ Build ID: 1834009c19946ab47de343deb97cbc50475fb96

Indeed no crash in the 4.0 branch, so REGRESSION.

Kind regards,
Joren
Comment 3 Christina Rossmanith 2013-05-28 07:57:02 UTC
The document opens fine here:

Version: 4.2.0.0.alpha0+
Build ID: f45cad5126137a868b9194c66b0eaa940eb6304
Linux

So it might be fixed in between and can be closed? Or should the fixing commit be found and applied to 4.1?
Comment 4 Julien Nabet 2013-05-28 19:59:43 UTC
Jorendc: I don't see how to add the fact we need a backtrace in https://wiki.documentfoundation.org/BugReport_Details. I saw it several times but don't remember :-)

Anyway, if someone wants to try to retrieve a bt, here's a link to help: https://wiki.documentfoundation.org/BugReport#How_to_get_a_backtrace_on_Windows
Comment 5 Jorendc 2013-05-28 20:01:52 UTC
@Julien: you meant that :)? (added 'want-backtrace' to keywords)
Comment 6 Julien Nabet 2013-05-28 20:06:20 UTC
Thank you Joren! I added it to this page: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Keywords#Keywords so I won't ask again:-)
Comment 7 Julien Nabet 2013-05-31 04:29:13 UTC
bfoman: would you have some time to give it a try? If you can reproduce, a backtrace would be useful.
(I can't reproduce this too with master sources on Debian)
Comment 8 Timon 2013-06-10 05:28:32 UTC
The same problem with Version: 4.1.0.0.beta2 Build ID: 33224f4f11a05cfad2249e812fcc2975fbb61f
Comment 9 Timon 2013-06-21 12:34:45 UTC
In LibreOffice Version: 4.1.0.1 Build ID: 1b3956717a60d6ac35b133d7b0a0f5eb55e9155 problem is fixed for me. Now document could be opened without any problems..
Comment 10 bfoman (inactive) 2013-06-21 13:53:54 UTC
Marking as RESOLVED WORKSFORME per comment 9.