summaryrefslogtreecommitdiff
path: root/src/OwnCloud_Documents_on_Arch_Linux.adoc
blob: 891a1d4e2f3c7e0641dbfc347e87cca4539f4d3b (plain)
    1 OwnCloud Documents on Arch Linux
    2 ================================
    3 :author: Aaron Ball
    4 :email: nullspoon@iohq.net
    5 
    6 
    7 == {doctitle}
    8 
    9 This is just a quick note for those folks who are running Arch Linux on their
   10 servers (I am). I was having trouble getting MS Word documents to render on my
   11 instance, despite having installed LibreOffice (fresh).  When I went to enable
   12 openoffice/libreoffice support, it errored out, telling me to check my logs,
   13 which gave me nothing more than an ambiguous 500 error (I checked the php,
   14 php-fpm, nginx, and owncloud logs). Finally, I su'd into the account that
   15 owncloud/php was running under and attempted to execute the libreoffice binary,
   16 which failed (Wooo! Useful output!). This is the error I received.
   17 
   18 ----
   19 Failed to open display
   20 javaldx: Could not find a Java Runtime Environment!
   21 Warning: failed to read path from javaldx /usr/lib/libreoffice/program/soffice.bin: error while loading shared libraries: libcups.so.2: cannot open shared object file: No such file or directory
   22 ----
   23 
   24 Most of that can be ignored as they are just warnings. There is one error
   25 however and that is the cups error (the last line).
   26 
   27 For LibreOffice to support document exporting, it needs cups (the daemon
   28 doesn't need to be running, we just need the library).
   29 
   30 Once you've got cups installed (__pacman -S cups__) and support enabled in
   31 ownCloud, you should be able to work on MS Word files in-browser.
   32 
   33 Category:ownCloud
   34 Category:Linux
   35 Category:Libreoffice
   36 
   37 
   38 // vim: set syntax=asciidoc:

Generated by cgit