Apache OpenOffice (AOO) Bugzilla – Issue 48180
Saving files sometimes not possible
Last modified: 2005-08-01 15:16:41 UTC
Sometimes it is impossible to save files. OO either creates no file at all, or zero-size files, and then reports a general error trying to save the file. After this happens once, it is never possible to save the file without restarting OO. (p.s. I don't know if framework is correct, feel free to recategorize...)
This was seen on two different Win XP machines, both SP2. This didn't happen in the 60s or 70s builds (I think), I think it started in the 80s.
Not reproducible in a more recent build like a 680m96 ! If this problem still remains, please provide more Info about the filesystem, about free discspace, where to save, what to save (example or attachment), ...
.
Please have a look in the backup directory (OOo installation path) if a file corresponding to the document you edited (maybe with another name) exists.
I had reproduced it once or twice by creating a writer document, saving it, printing to PDF, opening the PDF in Acrobat, and then (while it was still open) reprinting to PDF. I just tried this again and it didn't reproduce. Yesterday it happened with impress- I was playing with importing powerpoint slides and modifying the master slides, then suddenly saving didn't work. I'll attach the error dialog. Free diskspace it not a problem, filesystem is whatever's standard under XP (NTFS?), and it's happened with impress and writer docs on two separate machines.
Created attachment 25601 [details] Error dialog when saving is not possible
I looked for backup files under c:\Programme\OpenOffice.org 1.9.95 and did not see any backup files (or a directory)- where should they be?
Just happened again in Impress with .100 Started a blank presentation after installing .100, added two background graphic elements onthe master page, and started to create the presentation (5 pages at present). Nothing special in there, one more simple grey graphic on the title page, one 3x3 text table. Tried to save it in a newly created directory, and got a Write Error (see attachment). At this point I can't save it in amy format, including dumping it to PDF. Please give me some ideas on how to avoid this, since I lose my work every time this happens (well, copy, paste, reformat works, but isn't fun...) !
Created attachment 26015 [details] Write Error Dialog when saving not possible
More Info: - I rename it to test.odp, but the error dialog still refers to Untitled1. - it actually does create a 0 byte test.odp file when giving the error - the PDF file is created _successfully_ including all content, but I still get the error.
- saving as .otp creates a 0 byte file as well - saving as .ppt file doesn't create a file and gives a general output error (see first attachment) - after the general error, OO still has Untitled1 loaded, but all menus toolbars are deactivated as if the presenation did not exist. - creating another presentation in OO works, and it can be saved normally. - in Untitled1 I can still move items around, but can't edit any text - switching between normal/outline/notes/handout/slide sorter does not work either - over textboxes on rightclick I get only slide/grid/snap lines options, wit no subselections
- OO can't be closed (neither the document close nor the OO close) - killing the soffice.bin process and restarting OO brings up the recovery and crashreport tools - the recovery seems to successfully recover the last autosave (?) of the document, only one page (the last one to be created) was missing. - now saving works without any problems. - always create backup copy was OFF - Save AutoRecovery Information was OFF as well (now set to 5 minutes :)
- The state it gets hung up in (when it hangs up wiht the general error) is the save state: when I hit Ctrl-S to save a file, it is briefly in this state. Is there any way I can provoke a crash in that situation to at least get you a stacktrace or something?
Please try to describe the content of your presentation if you cannot attach a sample file. The 0 byte file creation is now fixed in a current version (m102) but the cause of the crash/error is not known. The problem seems to be an Impress problem only.
Perhaps the component should be changed to Drawing?
es: The content of the presentation (or the writer document when it occurred with that) seems irrelevant- i have nothing to reliably reproduce it with, or I would attach it. It seems to happen when playing with the master slides in Impress, and when changing a lot of styles in Writer. Unfortunately, I can't be more specific than that- sorry!
I have seen this under Linux (Suse 9.0) with build m109 within the writer component. It only seems to occur on documents where I have embedded charts or drawings. I'm attaching a strace output (zipped) obtained while attempting to save the document. Hopefully someone smarter than me can figure out the problem.
Created attachment 27465 [details] Strace output during saving when saving is not possible
Instructions to Reproduce 1) Open drawing.odg (attached testcase) 2) Copy its contents to the clipboard 3) Start a new text document 4) Paste clipboard to text document 5) Attempt to save text document Under m109 with both Linux and Windows saving is not possible.
Created attachment 27467 [details] Testcase (see comments for how to reproduce bug)
Testcase still fails under Linux / 680m113
testcase is reproducable with m113 (german localized version) on WinXP pro. I'm not shure about the component, so a developer should have a look.
We fixed several bugs about 'Saving is not possible' some are integrated in 1.9.m117 some in 1.9.m118 and one in 1.9.m119. Please have a look if the bug still occures in the latest version (1.9.m118). if the bug still occures please have a look again in the next version.
The problem still exists with m121 and is easy to reproduce with the testcase provided by openofficejac
Duplicate to issue 50824 *** This issue has been marked as a duplicate of 50824 ***
Normaly we close the newer issue but in this case the newer issue is already at the developer. Therefore I close this issue as duplicate.