Home New Forums discussions ProjectLibre Desktop Can’t open ProjectLibre on SLES 16: X11 connect error

Viewing 3 reply threads
  • Author
    Posts
    • #8840
      Roberto IbarraRoberto Ibarra
      Participant

      When I execute /opt/projectlibre/bin/ProjectLibre the following errors appear:

      rob@192:/opt/projectlibre/bin> ./ProjectLibre 
      opts:
      Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using ':0' as the value of the DISPLAY variable.
      	at java.desktop/sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
      	at java.desktop/sun.awt.X11GraphicsEnvironment$1.run(Unknown Source)
      	at java.base/java.security.AccessController.doPrivileged(Unknown Source)
      	at java.desktop/sun.awt.X11GraphicsEnvironment.initStatic(Unknown Source)
      	at java.desktop/sun.awt.X11GraphicsEnvironment.<clinit>(Unknown Source)
      	at java.desktop/sun.awt.PlatformGraphicsInfo.createGE(Unknown Source)
      	at java.desktop/java.awt.GraphicsEnvironment$LocalGE.createGE(Unknown Source)
      	at java.desktop/java.awt.GraphicsEnvironment$LocalGE.<clinit>(Unknown Source)
      	at java.desktop/java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(Unknown Source)
      	at java.desktop/java.awt.Window.initGC(Unknown Source)
      	at java.desktop/java.awt.Window.init(Unknown Source)
      	at java.desktop/java.awt.Window.<init>(Unknown Source)
      	at java.desktop/java.awt.Frame.<init>(Unknown Source)
      	at java.desktop/javax.swing.JFrame.<init>(Unknown Source)
      	at org.pushingpixels.flamingo.api.ribbon.JRibbonFrame.<init>(Unknown Source)
      	at com.projectlibre1.pm.graphic.frames.MainRibbonFrame.<init>(Unknown Source)
      	at com.projectlibre1.pm.graphic.frames.MainFrameFactory.creareMainFrame(Unknown Source)
      	at com.projectlibre1.pm.graphic.gantt.Main.main(Unknown Source)
      	at com.projectlibre1.main.Main.main(Unknown Source)

      Can this be because SLES 16 has dropped X11?:

      Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.

      TIA

    • #8843
      Project_LibreProject_Libre
      Keymaster

      If it’s empty or incorrect, and you are physically at the machine, you can try setting it manually:

      Bash
      export DISPLAY=:0
      ./ProjectLibre
      3. SSH with X11 Forwarding
      If you are connecting to this machine remotely via SSH, you can’t just run a GUI app without “tunneling” the graphics back to your local machine.

      Reconnect using the -X or -Y flag:

      Bash
      ssh -X [email protected].x.x
      Once connected, the DISPLAY variable is usually set automatically (often to something like localhost:10.0).

      Why this happens (The “X11 Architecture”)
      In the X Window System, the Server is actually the software managing your monitor and keyboard, while the Client is the application (ProjectLibre). Even if they are on the same physical box, they communicate via a protocol. If the “security cookies” (MIT-MAGIC-COOKIE) don’t match or the path is blocked, the Client (Java) panics because it has nowhere to “draw” its buttons and charts.

      A Quick Note on “Headless”
      If you are trying to run ProjectLibre on a server without a monitor just to process files, it won’t work this way. ProjectLibre requires a graphical environment to initialize. You would need a virtual framebuffer like xvfb to trick the app into thinking a screen exists.

    • #8998
      Roberto IbarraRoberto Ibarra
      Participant

      Thanks for your answer, I tried defining the DISPLAY variable and then running PL, but had the same result.

      As you said about the X Window System, it no longer exists in SLES 16, as It’s stated in that link I posted, can that be it?

      I am physically at the machine and it does has a monitor (2 actually).

      Thanks again.

    • #9533
      Roberto IbarraRoberto Ibarra
      Participant

      Solved: installed XWayland and now it is working.

Viewing 3 reply threads
  • You must be logged in to reply to this topic.