Bug 49209 - CRASH when FILEOPEN particular.odt from MS WORD 2010
Summary: CRASH when FILEOPEN particular.odt from MS WORD 2010
Status: RESOLVED DUPLICATE of bug 47436
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: All All
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-27 02:17 UTC by chagadaev
Modified: 2012-04-28 13:01 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Attachments
sample file (22.36 KB, application/vnd.oasis.opendocument.text)
2012-04-27 02:17 UTC, chagadaev 		Details
bt with symbols (14.19 KB, text/plain)
2012-04-28 12:59 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 chagadaev 2012-04-27 02:17:23 UTC 
Created attachment 60655 [details]
sample file

File d.odt was saved in MS Office 2010
When I try to open it, LibO crashes.
Comment 1 Nikolay Morozov 2012-04-27 03:46:44 UTC 
3.4.4 Linux file opens normaly
Comment 2 Rainer Bielefeld Retired 2012-04-27 08:50:40 UTC 
[Reproducible] with "LibreOffice 3.5.3.2 (RC2) German UI/Locale [Build-ID: 235ab8a-3802056-4a8fed3-2d66ea8-e241b80] on German WIN7 Home Premium (64bit) 

3.4.5 opens the document without problem.

3.5.3 opens sample document saved from 3.4.5 without problems.

LibO should not crash

@Cédric:
Please set Status to ASSIGNED and add yourself to "Assigned To" if you accept this Bug
Comment 3 Nikolay Morozov 2012-04-28 05:22:51 UTC 
3.5.2 Linux Crashes
Comment 4 Julien Nabet 2012-04-28 12:59:51 UTC 
Created attachment 60749 [details]
bt with symbols

On Debian x86-64, I reproduced the pb with 3.5 branch updated but partly compiled (I must recompile from scratch I think). So I attached the bt.
After having compiled editeng part specifically + deliver, I don't reproduce the problem.
Comment 5 Julien Nabet 2012-04-28 13:01:39 UTC 
I think the commit 1ad284007d898c68665c91979be3bd326c290ba1 which resolved fdo#47436 fixed too this problem.

If I'm wrong, don't hesitate to reopen.

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