On 03/01/2011 12:58 PM, Don C. Myers wrote:
Now if there was just a simple fix like that for LibreOffice base
working so sluggishly with Java 1.6.0_24!!!!!!!!
There is thread over on the OOo user list that mentions this.
Unfortunately the author doesn't provide any details or test scenario
(possibly due to the change of OOo website & lists):
<http://comments.gmane.org/gmane.comp.openoffice.questions/212275>
Perhaps if you can test with older versions of Java and create a valid
test scenario you can file a bug?
On 03/01/2011 02:50 PM, MR ZenWiz wrote:
On Tue, Mar 1, 2011 at 10:59 AM, NoOp<glgxg@sbcglobal.net> wrote:
On 03/01/2011 07:14 AM, Don C. Myers wrote:
I had the same issue, and found a fix on the Internet. I'm running
Ubuntu 10.10. Apparently this affected some OpenOffice installs. It
didn't affect me until I moved to LibreOffice. You need to modify your
hosts file as per the instructions here:
http://www.linuxquestions.org/questions/linux-software-2/double-clicking-on-open-office-files-leads-to-very-slow-opening-808048/
It worked perfectly for me.
...
Interesting! Thanks for that. Both OOo (standard) and LO show an intial
attempt on startup:
Seems like a bug that either should be querying $HOSTNAME.(none) - how
standard is that?
--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/users/
*** All posts to this list are publicly archived for eternity ***
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.