Issue 104838

Summary: Crash when saving file with Fontwork (from older version)
Product: General Reporter: cno
Component: codeAssignee: Oliver-Rainer Wittmann <orw>
Status: CLOSED DUPLICATE QA Contact: issues@framework <issues>
Severity: Trivial    
Priority: P2 CC: groucho266, issues, orw, stefan.baltzer
Version: DEV300m56Keywords: regression
Target Milestone: OOo 3.2   
Hardware: Unknown   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Attachments:
Description Flags
.odg that crashes on saving
none
.odt that crashes on saving none

Description cno 2009-09-06 14:48:36 UTC
Crash when saving file with Fontwork (from older version)
I will attach two files.
One .odg, one .odt
Both have an fontwork object, probably originating from 2005.
With bot files:
 - do some edit 
 - Ctrl-S
 > Crash
Also:
 - remove fontwork
 - Ctrl-S
 > No crash
Comment 1 cno 2009-09-06 14:54:39 UTC
Created attachment 64571 [details]
.odg that crashes on saving
Comment 2 cno 2009-09-06 14:55:12 UTC
Created attachment 64572 [details]
.odt that crashes on saving
Comment 3 cno 2009-09-06 14:56:40 UTC
Opening, editing and saving in 3.1.1 causes no crash
Comment 4 cno 2009-09-06 16:05:18 UTC
Error report ID's  rsmhtdc and rjkhtdc
Comment 5 cno 2009-09-06 18:13:56 UTC
and r2khtdc
Comment 6 Olaf Felka 2009-09-07 07:06:54 UTC
@ sba: Please have a look
Comment 7 stefan.baltzer 2009-09-14 17:00:23 UTC
Reproducible in DEV300_m58 on WinXP with both bugdocs.
I have sent crash reports, too ( Dont have the IDs yet)
Will search the winning developer tomorrow.
Comment 8 cno 2009-09-14 18:30:55 UTC
@sba: "Dont have the IDs yet" Is something for me ??
Comment 9 stefan.baltzer 2009-09-15 13:18:26 UTC
-> Cor: No, I just sent the report shortly before logging off. :-)

-> OD: Thank you for investigating. As discussed, please proceed by finding out
if this got already fixed this "along the way" in pending CWS dealing with other
stuff. 
Since this is a crash and regression in an average real-life document, OOo 3.2
should be the target, setting it now.
As said, no need to trigger formal showstopper alarm before sorting out if this
really needs a "new fix".
Comment 10 groucho266 2009-09-16 09:08:10 UTC
This is a duplicate to issue 100905.  The two issues are different to reproduce
but have the same root cause.

*** This issue has been marked as a duplicate of 100905 ***
Comment 11 groucho266 2009-09-16 09:08:43 UTC
Closing duplicate.