An interim reply - I'm tied up today (and all days to minor extent) with 
medical treatment - today I have morning and afternoon sessions.

It seems to be the case that the problem is caused by some peculiarity of the 
operating system.  I have checked on clean Xubuntu 14.04, 16.04 and 18.04 (64 
bit) installations, with OpenOffice 4.1.0 and 4.1.5 on each; no problem with 
rebuilding the Table of Contents on the test file. 

However, when I revert the test file to my normal computer (Xubuntu 16.04.03) 
the ToC takes hours to rebuild.  I tried the old trick of a fresh OO User 
Profile - no improvement.  This effectively rules out any side effects from all 
OO extensions installed on my normal computer, reducing the problem probably to 
some O.S. utilities on the affected computer.

I'll continue to investigate when I have time. 

Rory

On Mon, 01 Jan 2018 19:35:33 +0100
Andrea Pescetti <pesce...@apache.org> wrote:

> Rory O'Farrell wrote:
> > Andrea Pescetti wrote:
> >> The best archive build to use to the purpose would be the following:
> >> https://ci.apache.org/projects/openoffice/install/linux64/
> >> (5th entry)
> > I'll also try the OO 4.2.0 version you indicated.
> 
> For the record, I've tried it on my system (Ubuntu 14.04 LTS 64-bit, 
> trunk build from the link above) and it didn't show the issue: once 
> again I was able to perform the operation smoothly (a few seconds).
> 
> Again, if you can do just one test you should use a system where you can 
> reproduce the issue on any 4.1.x build, and try the trunk 
> archive/installed build there.
> 
> Regards,
>    Andrea.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 


-- 
Rory O'Farrell <ofarr...@iol.ie>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to