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]

Reply via email to