Member Avatar for n_e

I just updated Ubuntu to Lucid Lynx and also got an OpenOffice update: it's now 3.2. When I started it, the progressbar flashes to 100% in a second or two but to get from there to the actual program takes about two minutes. When I "top", I see that Java is using 100% CPU. I have a Core2 Duo with 4 GB. The previous Openoffice ran nice and fast.
Does anyone else have problem with the new Openoffice, or is it just me?

  • 3 Contributors
  • 4 Replies
  • 214 Views
  • 3 Months Discussion Span
  • Latest Post Latest Post by alaukik

Dani AI

Generated

This thread records a common pattern: OpenOffice hits the splash quickly but stays stuck while the Java VM or other subsystems initialize. Typical culprits are the JVM startup/extension loading, network name resolution, printer probing or a corrupted user profile — all can make a cold start take tens of seconds or minutes. ’s observation that the problem went away after a Lucid update fits with package/bug fixes; ’s pointer about Java and Quickstarter is one practical workaround already discussed here. (daniweb.com)

Quick diagnostics that clarify the cause (run as your regular user): check which Java is running and its bitness, inspect the process, and test local hostname resolution. Example commands:

java -version
ps aux | grep -i java
getent hosts $(hostname) || grep $(hostname) /etc/hosts

If java spins at 100% while OOo loads, the JVM initialization is a likely cause; if OOo is blocked on DNS lookups, the hostname->127.0.0.1 entry trick has fixed startup delays for others. (openoffice.org)

Next-step actions (ordered from least to most invasive): (1) verify/update the system JRE and ensure its 32/64-bit matches your OpenOffice build; (2) try a fresh user profile (rename the OpenOffice user profile directory so the suite recreates a clean one); (3) investigate printers/CUPS and any network services OpenOffice probes at start; (4) if you do not need Base/macros, the JVM can be disabled (tradeoffs apply) and Quickstarter reduces cold-start cost while using RAM. Each of these has tradeoffs, so test one change at a time. (openoffice.org)

If document compatibility or long-term maintenance matters, consider LibreOffice — it is the actively maintained fork with more frequent updates and stronger OOXML (.docx/.xlsx) work in recent years. If the issue is reproducible after testing the items above, file a bug with distro/OpenOffice details, include the java -version output and exact steps to reproduce. (newdesign2.libreoffice.org)

Recommended Answers

All 4 Replies

Member Avatar for richieking

Use geany. its in the repository, sudo apt-get install geany.

Comes in handy. also try gedit.

Explore :)

Member Avatar for n_e

You can't compare geany or gedit to the word processor of OpenOffice. I want to open/write Microsoft doc/docx types which can't be done with a simple program like gedit.
With the last update of Lucid Lynx this problem has disappeared for me, so I'll mark the thread as solved for now, although I would still like to know if other people have experienced the same problems..

Member Avatar for richieking

geany also compatible with doc/docx types.

That is why we love linux, there is always an alternative.

:)

Member Avatar for alaukik

BUMP

Go to Options Openoffice.org and then java then uncheck the box " Use a Java Runtime Environment" It speeds up Quite a bit
Also if you don't mind spending some of your ram you can enable quickstarter from the memory option it will fire up OOo it 1-2 Seconds!

commented: thanks +1
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.