My opinion would be to lodge a bug report since, although OS specific, it is important enough. OOo should provide some error checking so that this doesn't happen. Since I don't use Linux on a daily basis and since you've experienced it, the bug report would be best coming from yourself.
I've done a quick check in the bug DB and there does not seem to be any issues similar. Paul On Apr 11, 2005 6:51 PM, Rami Saarinen <[EMAIL PROTECTED]> wrote: > I apologize if this is old news. I tried to look this up from the bug > database, but did not find any similiar case. I considered to make a bug > report, but since this may be considered to be an OS issue and I was too > lazy to create an account just to make a single bug report so I decided > to post this to this newsgroup (this is not really a question, thought). > Maybe some of you will make this as a bug report if needed. You may also > contact me for further information. > > The problem: > A while ago we had to write quite a lot of reports for some schoolwork > and we were doing it in one of our Linux classes. Twice we managed to > lose most of our work as the documents came up scrambled and destroyed. > Later we found out that the problem was that Oo seems to write first in > the /tmp folder and when /tmp is full, the save is interrupted and the > cut-off version is written over the orginal one. > > -- > Rami Saarinen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
