Re: [api-dev] soffice -headless

2008-11-05 Thread kengentry5000

I am also trying to run Open Office in headless mode. I am trying to spawn an
soffice process from our Java app server to invoke an OpenOffice Basic macro
in an invocation very similar to yours. The process either hangs or exits
immediately without running the macro.

I followed one set of instructions to run the Xvfb test X server on a dummy
display value. OpenOffice launches without any windows as expected but will
not invoke the marco and seems to hang but may be just sitting idle. If
OpenOffice is launched without a macro parameter and backgrounded then
invoke again with the macro parameter it works.

I'm not sure which Xvfb version I downloaded but I did have to download an
updated version of the cairo 2D graphics library used by OpenOffice. The
older cairo library was not happy with Xvfb. The Xvfb invocation looks like
this (the :9 is the bogus DISPLAY value):

Xvfb -pixdepths 24 -co /usr/share/X11/rgb.txt -fp
/usr/share/X11/fonts/misc:/usr/share/X11/fonts/75dpi:/usr/share/X11/fonts/100dpi
:9

I am running OO v2.3.1 because it is supposed to be the first release that
can run headless but the last release that does not force a startup
licensing screen.

BTW - This is all running on a Linux Fedora Core 7 desktop system.

Did you make any progress getting this working?

Thanks,
Ken



Craig Johnson-6 wrote:
 
 
 I'm trying to run soffice in a cron job script where it executes in 
 -headless mode...
 
 e.g.
 
 soffice -headless macro://document/lib.module.macro
 file:///path/to/document
 
 ... but it dies with an error...
 
 Error : staroffice,v8.9 does not run without Openwindows
 
 If I set a valid DISPLAY var within the shell running the cron job it will
 work.
 
 Why does it need a valid DISPLAY var set if it's running in -headless
 mode?
 
 Is there something I can do in the shell script which runs the soffice 
 command to setup a valid DISPLAY var? I cannot just give it a made up 
 DISPLAY value unless I know that something is running for that DISPLAY.
 
 Thanks,
 Craig
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/soffice--headless-tp19789500p20342417.html
Sent from the openoffice - api dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] soffice -headless

2008-11-05 Thread Jan Füssel
Hi,

i've a similar scenario with an headless openoffice. The first version
of OpenOffice.org which i have sucessfully used in headless mode and
without xvfb is 2.4.1.

All previous version didn't work for me.

I hope this information could help you.

Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] soffice -headless

2008-11-05 Thread kengentry5000

I installed OO 2.4.2 and tried it. Initially it had the same behavior as OO
2.3.1 but then I had the thought to run the soffice process with sudo
(because I needed to install the package with sudo) and it works! There must
be some permissions issue causing me grief.

The system running our app is running as root so this will not be a problem.

So to summarize:
- Installed OO v2.4.2 with sudo (i.e. sudo ./setup)
- Invoked soffice first time interactively to do initial setup wizard and
licensing acknowledgement
- Did subsequent invocations of soffice with sudo (i.e. sudo /path to
OO/program/soffice macro

Thanks for your quick response

Ken


Jan Füssel wrote:
 
 Hi,
 
 i've a similar scenario with an headless openoffice. The first version
 of OpenOffice.org which i have sucessfully used in headless mode and
 without xvfb is 2.4.1.
 
 All previous version didn't work for me.
 
 I hope this information could help you.
 
 Jan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/soffice--headless-tp19789500p20343222.html
Sent from the openoffice - api dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] soffice -headless

2008-11-05 Thread kengentry5000

Does anyone have an idea of why running this with 'sudo' works but not
without? I removed OO v2.4.2 and reinstalled it my user directory without
sudo. I removed my ~/.openoffice* directories after install. I also ensured
the directories where file I/O is occurring are owned by my user account and
are writeable.

Another oddity is trying to pull up the macro security dialog locks up
openoffice unless I start soffice with sudo.

Any help understanding these user-mode limitations would be greatly
appreciated.

Ken


kengentry5000 wrote:
 
 I installed OO 2.4.2 and tried it. Initially it had the same behavior as
 OO 2.3.1 but then I had the thought to run the soffice process with sudo
 (because I needed to install the package with sudo) and it works! There
 must be some permissions issue causing me grief.
 
 The system running our app is running as root so this will not be a
 problem.
 
 So to summarize:
 - Installed OO v2.4.2 with sudo (i.e. sudo ./setup)
 - Invoked soffice first time interactively to do initial setup wizard and
 licensing acknowledgement
 - Did subsequent invocations of soffice with sudo (i.e. sudo /path to
 OO/program/soffice macro
 
 Thanks for your quick response
 
 Ken
 
 
 Jan Füssel wrote:
 
 Hi,
 
 i've a similar scenario with an headless openoffice. The first version
 of OpenOffice.org which i have sucessfully used in headless mode and
 without xvfb is 2.4.1.
 
 All previous version didn't work for me.
 
 I hope this information could help you.
 
 Jan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 

-- 
View this message in context: 
http://www.nabble.com/soffice--headless-tp19789500p20343462.html
Sent from the openoffice - api dev mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [api-dev] soffice -headless

2008-11-05 Thread Arthur

Hi

kengentry5000 wrote:

Does anyone have an idea of why running this with 'sudo' works but not
without? I removed OO v2.4.2 and reinstalled it my user directory without
sudo. I removed my ~/.openoffice* directories after install. I also ensured
the directories where file I/O is occurring are owned by my user account and
are writeable.

Another oddity is trying to pull up the macro security dialog locks up
openoffice unless I start soffice with sudo.

Any help understanding these user-mode limitations would be greatly
appreciated.


I don't have any experience with running the headless mode, but I 
frequently install OOo versions as user. I don't know how you're setup 
looks in detail. I always use 'alien -t' to convert the .rpm or .deb 
packages to .tgz packages, then I unpack them with a little for loop 
into a subdirectory. All this I do without ever being root (which was 
the reason I've done it the first time, later I've simply used it to 
play with different OOo versions without making a mess in my system 
setup). Works like a charm for me.


Good luck

Arthur


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[api-dev] soffice -headless

2008-10-02 Thread Craig Johnson


I'm trying to run soffice in a cron job script where it executes in 
-headless mode...


e.g.

soffice -headless macro://document/lib.module.macro file:///path/to/document

... but it dies with an error...

Error : staroffice,v8.9 does not run without Openwindows

If I set a valid DISPLAY var within the shell running the cron job it will work.

Why does it need a valid DISPLAY var set if it's running in -headless mode?

Is there something I can do in the shell script which runs the soffice 
command to setup a valid DISPLAY var? I cannot just give it a made up 
DISPLAY value unless I know that something is running for that DISPLAY.


Thanks,
Craig




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]