Apache OpenOffice (AOO) Bugzilla – Issue 22270
Lost presentation graphics
Last modified: 2004-01-30 08:57:57 UTC
All graphics (which I had originally inserted from files, but at different times) were missing at my latest opening of my Impression file - "broken graphic" symbols are in their place. I tried opening the file several times, rebooting once, all with same result. I have made no system changes since my last use (yesterday) when the graphics _did_ appear FYI I spent 30 minutes trying to use your system to "find an issue" regarding my problem, but _none_ of searchs I did returned a hit, so if there is an existing issue report on this topic don't blame me for not trying to find one! [PS I had once tried to use OO 1.0.1 and given up due to its bugs and instead started using Koffice, but decided to try 1.1 to see if if was any better - but if it's going to destroy what I have already taken pains to create then there is certainly no point trying to use it!]
After more work, I believe that this problem is connected with the additional problem that Impression always wants to save my file with a password - even if I have previously forced it to save the file without a password. And if is saved with a password them I cannot get access to the graphics. The only way that I have found to prevent the file from being saved with a password is at _each_ file opening go to "Save as" and unclick the "save with password" box and then save (overwriting) the file. Subsequent saves in the same session work correctly, without adding a password. But god help me if I should ever forget to do the "save as without password" step on opening the file, as then a password requirement will be added and I will never get the graphics back!
Reassigned to Christian.
This is a known bug which will be fixed in OOo1.1.1 I set this issue as duplicate to issue 22235 *** This issue has been marked as a duplicate of 22235 ***
This issue is duplicate to issue 22235 Issue 22235 is fixed and integrated in OOo 1.1.1 I close this issue. Please reopen it if the bug still occures in OOo1.1.1.
I close the issue