[upstream] OpenOffice autosaves during activity like dragging objects

[Adam Porter]

Binary package hint: openoffice.org-impress

I am working on a large presentation that includes many photos. It takes a while to save the presentation to disk because of all the photos (it's over 300MB right now). Just now while I was dragging an image object to another place on a slide, the autosave kicked in, which stopped me from doing anything until the save completed. This is quite annoying. OO should be smart enough to avoid this.

[Venkatraman.S (blizzardz)]

This can happen as AutoSave is On . It is disabled by default.
Can you try changing the settings (Tools -> Options, and then go to the Load/Save -> General tab. Tick the "AutoSave every" option and enter a BIG time, say 1hour) and try this.
Here you have the choice to also disable the "Always create backup copy" option.

Reopen the bug if the problem still persists. Thanks for reporting this and making Ubuntu better.

[Adam Porter (alphapapa)]

Your suggestion merely defeats the purpose of AutoSave; it doesn't solve the problem. Setting AutoSave to one hour means that it will only autosave once an hour, so if OO crashes during that time, all changes will be lost. The whole point is to autosave often, so that if it crashes, you won't lose much.

I already explained the problem, and that OO should be smart enough to avoid the behavior of autosaving while you're moving an object, etc.

Your reply does not address solving the actual problem.

[Chris Cheney (ccheney)]

Upstream wants to know if you still have this problem with OpenOffice.org 3.0.

[Adam Porter (alphapapa)]

Please forgive the following, but I think this is another example of poor bug-tracking and poor end-user relations. It seems like, instead of a developer checking the code to see if it has been updated to fix this problem, I'm asked to download a large new major release. It seems like many Ubuntu bug reports are handled this way: instead of the developer checking the code, the end-user is asked to check a newer version, over and over again. Contrast this with Debian, where it seems like they actually look into the problem and determine whether an attempt to fix it has been made before asking the user to try a newer version--unless the user wasn't using the latest release when he filed the bug.

[Chris Cheney (ccheney)]

So you believe a 300MB document is a standard use case?

Feel free to put the document somewhere that I can download it and test with if you are upset at the request of testing the upstream version. They (Sun) refuse any bugs reported to them unless it can be proved to happen on their version as well.

[Adam Porter (alphapapa)]

On Thu, Oct 23, 2008 at 20:26, Chris Cheney <email address hidden> wrote:
> So you believe a 300MB document is a standard use case?

Well, you might be surprised at how many PowerPoint users make
presentations full of large, unresized digital photos. Theoretically,
if PowerPoint can do it, why not Impress? :)

> Feel free to put the document somewhere that I can download it and test
> with if you are upset at the request of testing the upstream version.
> They (Sun) refuse any bugs reported to them unless it can be proved to
> happen on their version as well.

I appreciate your offer--that's above and beyond the call of duty--but
I'll try to test it myself.

[Chris Cheney (ccheney)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!