I wrote:

> When I get home I'll see if I can get the rpm which I've just discovered:
> ftp://fr2.rpmfind.net/linux/fedora/linux/releases/20/Everything/i386/os/Packages/l/libreoffice-4.1.3.2-9.fc20.i686.rpm
> to work in F22 with ctwm.

Of course, there were lots more rpms to be included.

However, I changed my mind and did some google searching. There were several
places where people were complaining about rendering problems. Then someone
suggested trying a pre-release version. I found two (4.4.4 and 5.0.0) at
the bottom of this page:

    http://www.libreoffice.org/download/libreoffice-fresh/

So I selected version 5, the latest, and since I think my current version of
ctwm was built on a 32 bit fedora, I opted for 32 bit LO, although I now
run 64 bit fedora 22.

These were the options displayed:

    Linux x64 (deb)
    Linux x64 (rpm)
    Linux x86 (deb)
    Linux x86 (rpm)  <-- here

I fetched the x86 rpms for main installer, English(GB) interface and
English(GB) help rpm.

Not all the required additional libraries were automatically fetched.
But when I got an error message 'xxx' missing, looked for names of
64 bit packages with 'xxx' included, added .i686 and installed them.

I kept a record of all of those extra installs required, in case
anyone else wants the list.

After that, the LO installation completed, but it would not start up properly.

>From the error messages I found what else needed to be installed, including
java. (I selected openjdk (32 bit), which may have been the wrong java).

After that it started, and colour and highlight menus now work perfectly.
A few 'difficult' powerpoint slides also work.

However I still get this warning printed out whenever LO starts:

    javaldx: Could not find a Java Runtime Environment!
    Warning: failed to read path from javaldx

That seems to come from this file:

    /opt/libreoffice5.0/program/javaldx

But I have no idea why, or how to disable the apparently pointless warning.

Summary: it seems that either replacing 64 bit LO with 32 bit LO, or installing
a later version of LO, or both, allowed, me to get LO working in my 32 bit ctwm,
including colour menus. So I don't need to switch to OpenBox!

I'll now do the same on my laptop, after some sleep.

I hope this information is of some use.

Aaron

Reply via email to