You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2016/04/15 18:45:25 UTC

[jira] [Resolved] (OPENMEETINGS-1375) JODConverter not working with libreoffice though libreoffice is installed and JOD path is rightly placed

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-1375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved OPENMEETINGS-1375.
--------------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 3.1.1)

I believe this is not OM issue
please ensure you have latest JOD available
and openmeetings.log to get exit codes, commands
please contact user@ list to get further help

> JODConverter not working with libreoffice though libreoffice is installed and JOD path is rightly placed
> --------------------------------------------------------------------------------------------------------
>
>                 Key: OPENMEETINGS-1375
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1375
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Converters
>    Affects Versions: 3.1.1
>         Environment: OpenSuse 42.1 running in t2.micro instance on AWS server.
>            Reporter: Rodrigo Petrus Domingues
>            Assignee: Maxim Solodovnik
>
> JODConverter not working with libreoffice though libreoffice is installed and JOD path is rightly placed.
> I have another server instance of OpenMeetings that is working correctly in my local (test) server. When the setup was not right, the errors were explicitly displayed. In my server on the cloud the conversion is not working and there is no visible explanation of what occurred. Both configuration of jod path's and the jod API is equal and the latest stable version.
> My local server runs on Ubuntu 14.04. Both libreoffice versions were installed from their respective package repositories.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)