I introduce this bug report because it affects the version recommended by the wiki to use LibreOffice "Impress remote control". (LibreOffice 4.0.1 RC1 (2013-02-22)) Trying to start LibreOffice from the GUI does not start this. When you try through the terminal, it returns the following message:"Warning: failed to read path from javaldx no suitable windowing system found, exiting" Tested on: Fedora 18 32-bit Gnome 3.6.2 LibreOffice 4.0.1.1 The package was downloaded from the website of pre-releases (RPMs) and installed such integration. Thanks
Does... yum -y install libpng12 make it work ? If so, its a duplicate of bug 61571
(In reply to comment #1) > Does... > > yum -y install libpng12 > > make it work ? > > If so, its a duplicate of bug 61571 If it works. For a formatting error in the previous message was confusing to understand the error that I got. The error message was: Warning: failed to read path from javaldx suitable no windowing system found, exiting The first error was resolved by deleting the LO configuration in the folder ".config". The second error has been resolved with the advice you gave me. As the cause of the first error is just carelessness, would be considered a duplicate bug report 61571 thank you very much
(In reply to comment #2) > If it works. For a formatting error in the previous message was confusing to > understand the error that I got. The error message was: > > Warning: failed to read path from javaldx > suitable no windowing system found, exiting > > The first error was resolved by deleting the LO configuration in the folder > ".config". The second error has been resolved with the advice you gave me. > > As the cause of the first error is just carelessness, would be considered a > duplicate bug report 61571 "Warning: failed to read path from javaldx" is generally a harmless warning that merely indicates that some data LO had cached about which JRE to use had become stale, and would typically self-heal, latest when you do something in LO that actually requires Java.
*** This bug has been marked as a duplicate of bug 61571 ***