Ahhh, I missed this mail ;-)

As Stephan said, it is probably better to ask on the go-oo lists or to switch to vanilla (http://download.openoffice.org).

Regards

     Kay


Stephan Bergmann wrote:
On 11/12/09 18:49, Lukasz Szybalski wrote:
I did not see my application fail or get disconnected in non-headless mode.
I do see it failing in headless.
[...]
Are there any differences in headless vs non-headless? Is there a
different mailing list I should be asking these questions? (headless
mailing list?)

I asked Philipp Lohmann from the VCL team (relevant list would be [email protected]) if he knows about any stability issues with headless mode, but he had nothing to offer. If the cause for the unexpected connection closure is a crash of OOo, I guess you will need to attach a debugger to OOo so we can find out more.

 aptitude show openoffice.org-headless
Package: openoffice.org-headless
New: yes
State: installed
Automatically installed: no
Version: 1:2.4.1+dfsg-1
Priority: optional
Section: misc
Uncompressed Size: 2347k
Depends: openoffice.org-core (= 1:2.4.1+dfsg-1), libc6 (>= 2.7-1),
libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1),
         libstlport4.6ldbl
Description: Headless VCL plugin for OpenOffice.org
 OpenOffice.org is a full-featured office productivity suite that
provides a near drop-in replacement for Microsoft(R)
 Office.

maybe I should try go-oo.org?

Reportedly, go-oo used a different implementation of headless than vanilla OOo in the past, but probably have converged to the vanilla one by now. (But the above output suggests that you still use OOo 2.4.1, which is really old. Use OOo 3.1.1 or snapshots of the forthcoming OOo 3.2 instead!) In any event, if you are using OOo based on the go-oo fork, it is probably best to ask there first.

-Stephan

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to