Bug#222731: Even more info

2003-12-11 Thread Juanjo Alvarez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Dec 10, 2003 at 03:27:51PM +0100, Chris Halls wrote: > Good work, thanks. Do you still have an .openoffice directory that has > the problem somewhere, or can you now no longer reproduce the problem? Unfortunately after some use OO has starte

Bug#222731: Even more info

2003-12-10 Thread Chris Halls
On Wed, 2003-12-10 at 14:36, Juanjo Alvarez wrote: > I've found that just deleting the .openoffice directory on a user > directory fixes the problem for that user. Good work, thanks. Do you still have an .openoffice directory that has the problem somewhere, or can you now no longer reproduce the

Bug#222731: Even more info

2003-12-10 Thread Juanjo Alvarez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 More info: I've found that just deleting the .openoffice directory on a user directory fixes the problem for that user. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/1yFP7WKWOGMJ2fkRAikYAJwINQikeVTyBfCXzymtEwd7dhYrvgCfaX31 J

Bug#222731: Even more info

2003-12-10 Thread Juanjo Alvarez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've looked at the strace output. It seems that 99% of the (huge) time is spend doing something related to fonts. 99% of the output is like: 17:15:02 lseek(18, 48937584, SEEK_SET) = 48937584 17:15:02 lseek(18, 0, SEEK_CUR) = 48937584 17:15: