Issue 1186 - drawing causes OpenOffice 632 to crash
Summary: drawing causes OpenOffice 632 to crash
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: 632
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: wolframgarten
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-07-07 15:19 UTC by issues@www
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

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

Attachments
OpenOffice drawing the exhibits the problem (5.45 KB, application/octet-stream)
2003-12-06 14:52 UTC, issues@www 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description issues@www 2001-07-07 15:19:09 UTC 
A drawing file that can be opened in OpenOffice 627 (and saved by 627) causes
OpenOffice 632 to crash. I have made the file available
http://gramps.sourceforge.net/bug632.sxd.

This problem occurred on RedHat 7.1, with the binary installation for 632. The
drawing file was originally created by the genealogoy program "gramps". The
"gramps" generated file caused OO632 to crash. I then copied the file to a WinME
machine running build 627. Build 627 was able read the file, so I saved it to a
new file, to create a file that was directly generated by OpenOffice (in case
"gramps" had done something incorrectly when it generated the file). I then
brought the new OpenOffice generated file back to the Linux box, and recieved
the same crash.
Comment 1 issues@www 2001-07-07 15:47:54 UTC 
Created attachment 356 [details]
OpenOffice drawing the exhibits the problem
Comment 2 bettina.haberer 2001-07-17 09:24:51 UTC 
Reassigned to Wolfram.
Comment 3 wolframgarten 2001-10-10 10:02:08 UTC 
Hello,
 could you please try to reproduce the bug on an actual version 638? I have tested this and had no problemsopening the sended file. Thanks.
Comment 4 wolframgarten 2001-10-10 14:11:40 UTC 
I close this bug now.
Don Allingham has wrote in an email that he has verified that bug and
 the problem has gone away in 638.