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:
Please attach an original document as an example which does this
Created attachment 116745 [details] The document causing the problem
Created attachment 116750 [details] screenshot taken from 1.1.3-11.5.0.fc3
Created attachment 116751 [details] screenshot opened in openoffice.org-1.9.117-1.2.0.fc5
Created attachment 116752 [details] saved and reloaded in the rawhide version
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 ?
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.
ah!, I'm blind. This is probably a generic thing in ooo2.0, I'll build a small test case and hassle upstream
moved the bug to openoffice.org bugtracker, http://qa.openoffice.org/issues/show_bug.cgi?id=51983