Issue 59280 - Crash when saving a MS-Word RTF file in odt or in swx format
Summary: Crash when saving a MS-Word RTF file in odt or in swx format
Status: CLOSED DUPLICATE of issue 59345
Alias: None
Product: Writer
Classification: Application
Component: save-export (show other issues)
Version: OOo 2.0
Hardware: PC All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-13 11:22 UTC by pamodeo
Modified: 2013-08-07 14:42 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
#1 - RTF file causing the crashes (text/rtf) (53.38 KB, text/rtf)
2005-12-13 11:23 UTC, pamodeo
no flags Details
#2 - MS Word 97 file successfully saved from #1 (14.00 KB, application/msword)
2005-12-13 11:24 UTC, pamodeo
no flags Details
#3 - RTF file successfully saved from #1 (33.69 KB, text/rtf)
2005-12-13 11:25 UTC, pamodeo
no flags Details
#4 - ODT file successfully saved from #2 (9.09 KB, application/vnd.oasis.opendocument.text)
2005-12-13 11:28 UTC, pamodeo
no flags Details
#5 - ODT file successfully saved from #3 (12.50 KB, application/vnd.oasis.opendocument.text)
2005-12-13 11:30 UTC, pamodeo
no flags Details
#6 - Oo2 crash log message (6.28 KB, text/plain)
2005-12-13 11:31 UTC, pamodeo
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description pamodeo 2005-12-13 11:22:37 UTC
Crash observed when saving a RTF file (attach. #1) either in odt or in swx
format. Saving in doc (97) (attach. #2) or rtf again (attach. #3) works and both
new files can be safely read and saved in odt, although they look different
(attach. #4 and #5). I also attach Oo2 crash message (attach. #6).
Same crash observed if the original rtf file is modified before saving.
Other files, presumably generated with the same MS-Word version are saved
without problems.

Note that: 
1) I'm running FC4 (kernel 2.6.14-1.1644_FC4) on a Toshiba Pentium IV laptop.
2) Video drive IS nvidia (NVIDIA-Linux-x86-1.0-7676-pkg1).
3) Soon before the crash, I yum-updated the system including some VERY new GNOME 
   and GNOME-related packages (i.e. gnome-desktop-2.12.1-1.1.fc4.nr).
Comment 1 pamodeo 2005-12-13 11:23:54 UTC
Created attachment 32335 [details]
#1 - RTF file causing the crashes (text/rtf)
Comment 2 pamodeo 2005-12-13 11:24:33 UTC
Created attachment 32336 [details]
#2 - MS Word 97 file successfully saved from #1
Comment 3 pamodeo 2005-12-13 11:25:40 UTC
Created attachment 32337 [details]
#3 - RTF file successfully saved from #1
Comment 4 pamodeo 2005-12-13 11:28:15 UTC
Created attachment 32338 [details]
#4 - ODT file successfully saved from #2
Comment 5 pamodeo 2005-12-13 11:30:31 UTC
Created attachment 32339 [details]
#5 - ODT file successfully saved from #3
Comment 6 pamodeo 2005-12-13 11:31:15 UTC
Created attachment 32340 [details]
#6 - Oo2 crash log message
Comment 7 michael.ruess 2005-12-13 16:15:47 UTC
MRU->FLR: this attachment will crash OO 2.0.1 when opening. Must be fixed in 2.0.2.
Comment 8 andreas.martens 2006-01-13 09:17:17 UTC
Introduced by numtree?
Stack:
SwCntntNode::GetNoCondAttr(unsigned short nWhich = 0x40, ...
SwTxtNode::_GetNumRule(unsigned char bInParent = 0x1 '') ....
SwTxtNode::GetNumRule(unsigned char bInParent = 0x1 '')...
SwUnoCursorHelper::getCrsrPropertyValue(...
Comment 9 Oliver-Rainer Wittmann 2006-01-13 11:13:49 UTC
Together with AMA I figured out the following:
On opening the RTF document in SRC680m149 the following assertion comes up:
(1) "nothing in this frame, not legal" from the RTF import filter.
(2) "NoTxt neighbour of Txt" from the layout engine.
The crash on opening is triggered by the collection of words for word completion
or the AutoSpellCheck caused by an inconsistent document core - see the assertions.
If collection of words for word completion and the AutoSpellCheck are switched
off, the document can be loaded.
The crash on saving this loaded document to OpenDocument file format is also
triggered by the inconsistent document core.
Thus, the defect isn't caused by cws swnumtree.

But, this defect is already fixed by issue i59345 in cws swqbf48.

OD->MRU: please verify and close this issue.
Comment 10 Oliver-Rainer Wittmann 2006-01-13 11:17:55 UTC
mark as duplicate

*** This issue has been marked as a duplicate of 59345 ***
Comment 11 michael.ruess 2006-01-27 14:29:47 UTC
closed, fixed in 680m153 build.