Bug 163234 - Unable to correctly open old open office draw files
Unable to correctly open old open office draw files
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Caolan McNamara
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-14 08:25 EDT by Simon Goodall
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-07-14 12:28:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
The document causing the problem (2.48 MB, application/x-tar)
2005-07-14 09:06 EDT, Simon Goodall
no flags Details
screenshot taken from 1.1.3-11.5.0.fc3 (245.60 KB, image/png)
2005-07-14 09:50 EDT, Caolan McNamara
no flags Details
screenshot opened in openoffice.org-1.9.117-1.2.0.fc5 (246.18 KB, image/png)
2005-07-14 09:53 EDT, Caolan McNamara
no flags Details
saved and reloaded in the rawhide version (238.92 KB, image/png)
2005-07-14 09:54 EDT, Caolan McNamara
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenOffice.org 51983 None None None Never

  None (edit)
Description Simon Goodall 2005-07-14 08:25:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
I have a Draw document created in open office under fc3. When I try opening it in open office on fc4, drop shadows have been added to a large number of the images in the document when previously there were not.
Additionally, when saving the document in the new format, it incorrectly saves the path to the images so that next time it is opened, it cannot find them. It misses out one of the directories.

E.g.
/home/user/Poster/pics/pic1.png
becomes
/home/user/pics/pic1.png



Version-Release number of selected component (if applicable):
1.9.112

How reproducible:
Always

Steps to Reproduce:
1. Open an old oo draw document.
2. notice that drop shadows have appeared where they should not.
3. Fix errors.
4. Save in new format.
5. Close old document
6. Open new document
7. See lots of warnings about missing files

  

Actual Results:  see above

Expected Results:  First case, oo2 show display the doc the same as in the old oo
Second case, oo  should have found the pictures 

Additional info:
Comment 1 Caolan McNamara 2005-07-14 08:58:39 EDT
Please attach an original document as an example which does this
Comment 2 Simon Goodall 2005-07-14 09:06:19 EDT
Created attachment 116745 [details]
The document causing the problem
Comment 3 Caolan McNamara 2005-07-14 09:50:37 EDT
Created attachment 116750 [details]
screenshot taken from 1.1.3-11.5.0.fc3
Comment 4 Caolan McNamara 2005-07-14 09:53:58 EDT
Created attachment 116751 [details]
screenshot opened in openoffice.org-1.9.117-1.2.0.fc5
Comment 5 Caolan McNamara 2005-07-14 09:54:47 EDT
Created attachment 116752 [details]
saved and reloaded in the rawhide version
Comment 6 Caolan McNamara 2005-07-14 09:59:50 EDT
looks about right to me when opened in 1.1.3 and then opened with the rawhide
version. I'll push an fc4 update to be the same version as the rawhide one as
soon as I can. These screenshots are how you would expect it to look ?
Comment 7 Simon Goodall 2005-07-14 11:10:03 EDT
The screenshot (openoffice.org-1.9.117-1.2.0.fc5) shows drop shahows on the
images above the class: XXXX boxes. These are not in the original file.
When fixing these and saving, the bad path name error seems to get introduced.
Comment 8 Caolan McNamara 2005-07-14 12:08:57 EDT
ah!, I'm blind. This is probably a generic thing in ooo2.0, I'll build a small
test case and hassle upstream
Comment 9 Caolan McNamara 2005-07-14 12:28:06 EDT
moved the bug to openoffice.org bugtracker,
http://qa.openoffice.org/issues/show_bug.cgi?id=51983

Note You need to log in before you can comment on or make changes to this bug.