Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


On 11/28/2012 04:52 PM, Ignaz Forster wrote:
Am 28.11.2012 13:33, schrieb Andrew Haley:
On 11/28/2012 10:45 AM, Ignaz Forster wrote:
- Download
http://wollmux.googlecode.com/files/wollmux-11.10a-manual_installation.zip
- Extract the file WollMux.oxt
- Install the plugin: unopkg add /path/to/WollMux.oxt (or, if unopkg
isn't installed, use Tools ->  Extension Manager in LibreOffice)
- export OOO_FORCE_DESKTOP=kde4
- Close all LO instances and start LibreOffice Writer (lowriter)

Now just open Tools ->  Extension Manager a few times. It usually crashes
the second time the dialog comes up...


In case it isn't crashing, restart LibreOffice and/or make sure you are
really using the KDE4 frontend (on a default KDE4 installation, the file
open dialog should look like the right side of this picture:
http://news.opensuse.org/wp-content/uploads/2012/09/integration-shadow-300x227.png)

It's really using the KDE4 frontend and it doesn't crash.

LibreOffice 3.5.7.2
Build ID: 350m1(Build:2)

OpenJDK Runtime Environment (fedora-2.3.3.fc17.1-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)

Hmmm... strange.
I've just tried this setup using a Fedora 17 KDE Spin Live CD, so 
LibreOffice and OpenJDK versions are exactly the same - and it's crashing.

Is this on a single or a multicore CPU?

Multi.  I wonder if there's something you've been doing that I haven't.

Andrew.


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.