Calc very slow to load document. Write slow to print

[arubin]

Running Open Office 2.4 in Linux, slackware 11

Calc is taking ages to load a small spreadsheet. My PC takes 3 seconds to load calc but loading a small spreadsheet takes 18 seconds!

It was much faster previously. Something has happened to slow it but I have no idea what.

I have tried uninstalling it, deleting .open-office and re-installing but it makes no difference.

Similarly it takes ages to print up the print dialog when printing.

Any ideas what could be slowing things down?

Thanks

[acknak]

I don't know what might cause a slowdown, but I have some questions from your description:

There is no "Open Office 2.4" (yet). Was that a typo?

Are your files local (i.e. not over a network)?

Have you changed anything recently (especially your printer configuration)?

Is it only existing document that are slow? If you create and save a brand new spreadsheet, does that also take a long time?

[arubin]

Sorry. Away from my home PC now but I think it is 2.0.4

Files are local.

I did change the priinter configuration in cups to allow printing over my home network. But the printer is connected to this PC through the parallel port. No other programs print slowly.

I think that brand new spreasheets are also slow but will check tonight.

[acknak]

Look carefully at the printing: this kind of delay is very typical of a document that calls for a particular printer. At some later time that specific printer is configured away, but OOo continues to try and access it using the old name, which involves a wait of some seconds before giving up. You may simply need to use the File > Print dialog to re-select the (new?) printer name.

[arubin]

Well I have changed the default printer to kprinter so bringing up the kde dialog rather than going directly. That works better.

I am still having the problem with spreadsheets, including new spreadsheets

[acknak]

Hmm. Well, if you are using 2.0.4, you may want to try the latest OOo version. There have been many improvements since 2.0.4, but of course I can't say for sure that it would fix your problem.