EPrints Technical Mailing List Archive
Message: #03040
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: OpenOffice failed to start
- To: "'eprints-tech@ecs.soton.ac.uk'" <eprints-tech@ecs.soton.ac.uk>
- Subject: [EP-tech] Re: OpenOffice failed to start
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Mon, 19 May 2014 13:51:39 +0100
Hi, You’re right, I got the log file path wrong. Do you also have an openoffice.pid file in the ~/var/ directory? Is the ownership on that directory OK for the user to create a file in there (e.g. can the pid file get created)? I *think* you need to reference the soffice.bin directly. I have: $c->{executables}->{openoffice} = '/usr/lib64/libreoffice/program/soffice.bin'; $c->{executables}->{python} = '/usr/bin/python'; $c->{executables}->{uno_converter} = "$c->{base_path}/bin/DocumentConverter.py"; I think that python is only needed for uno_converter. If you just run openoffice without other parameters, does it start OK? If not, can you run it as root? Cheers, John From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of Jacob Wenzel Thanks again! On 19-05-2014 13:07, John Salter wrote:
|
- References:
- [EP-tech] OpenOffice failed to start
- From: Jacob Wenzel <jw@energiakademiet.dk>
- [EP-tech] Re: OpenOffice failed to start
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] Re: OpenOffice failed to start
- From: Jacob Wenzel <jw@energiakademiet.dk>
- [EP-tech] Re: OpenOffice failed to start
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] Re: OpenOffice failed to start
- From: Jacob Wenzel <jw@energiakademiet.dk>
- [EP-tech] OpenOffice failed to start
- Prev by Date: [EP-tech] Re: OpenOffice failed to start
- Next by Date: [EP-tech] Re: OpenOffice failed to start
- Previous by thread: [EP-tech] Re: OpenOffice failed to start
- Next by thread: [EP-tech] Re: OpenOffice failed to start
- Index(es):