From: Herman Roozenbeek <herman.roozenbeek@tiscali.nl>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] openoffice-bin-2.0 : slow start
Date: Thu, 27 Oct 2005 19:30:24 +0200 [thread overview]
Message-ID: <43610EB0.7010109@tiscali.nl> (raw)
In-Reply-To: <4360EE8C.1090307@gmail.com>
Jonathan Schaeffer wrote:
> Hi *,
>
> I emerged openoffice-bin v2.
> When I start ooo2-writer, it's taking an eternity : about 75 seconds
> (ok, it'a pretty short eternity)
>
> Has anybody seen this issue ? May it be due to blackdown java ?
It's a well known issue by now. Most people (including me) seem to fix
it by disabling Java in the OO.org-configuration (Tools > Options >
OpenOffice.org > Java). After that, startup time will be more acceptable.
Success!
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-10-27 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 15:13 [gentoo-amd64] openoffice-bin-2.0 : slow start Jonathan Schaeffer
2005-10-27 17:30 ` Herman Roozenbeek [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-27 15:19 Dmitri Pogosyan
2005-10-27 19:30 ` Dominik Karall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43610EB0.7010109@tiscali.nl \
--to=herman.roozenbeek@tiscali.nl \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox