Topic
8 replies Latest Post - ‏2007-10-09T14:23:15Z by SystemAdmin
ramso
ramso
5 Posts
ACCEPTED ANSWER

Pinned topic X-Window Application

‏2007-04-18T15:52:55Z |
We are trying to start a xwindow application, like xlogo, but the process send a error [b]can't open display :0.0[/b]. We are test this with the local console of the server with a sesion open in this display , and with the display close.
We are changed the display var with the same result, we are testing with remote server, freenx and vnc and the same.
I think we make something wrong, any idea ?
Updated on 2007-10-09T14:23:15Z at 2007-10-09T14:23:15Z by SystemAdmin
  • ramso
    ramso
    5 Posts
    ACCEPTED ANSWER

    Re: X-Window Application

    ‏2007-04-18T16:10:00Z  in response to ramso
    I test now with a vnc and work fine.
  • ramso
    ramso
    5 Posts
    ACCEPTED ANSWER

    Re: X-Window Application

    ‏2007-04-18T16:40:44Z  in response to ramso
    With freenx it's necessary to change the display and use the hostname of the server.
  • SystemAdmin
    SystemAdmin
    90 Posts
    ACCEPTED ANSWER

    Re: X-Window Application

    ‏2007-04-18T18:27:18Z  in response to ramso
    When you start the session, first set the xhost command by typing "xhost +"
    Then you start the p_AVE by running "runx86"
    Once you are in the p_AVE environment, please export your display by typing
    "export DISPLAY=localhost:x:0" where x is the port number
    • ramso
      ramso
      5 Posts
      ACCEPTED ANSWER

      Re: X-Window Application

      ‏2007-04-19T07:13:14Z  in response to SystemAdmin
      This run in remote session like vnc o freenx, but in local session don't work.
      • SystemAdmin
        SystemAdmin
        90 Posts
        ACCEPTED ANSWER

        Re: X-Window Application

        ‏2007-04-19T14:53:59Z  in response to ramso
        Could you please provide me more detail on local session. It will also help if you can provide the steps you did.
        • ramso
          ramso
          5 Posts
          ACCEPTED ANSWER

          Re: X-Window Application

          ‏2007-04-20T07:53:59Z  in response to SystemAdmin
          We have a OpenPower with the Matrox graphic card installed. We start the Xwindow in this local console for root access. In a normal user X sesion, with kde, we open a console and test the display, DISPLAY=:0.0, it's rigth. Start the x86 and control the display, DISPLAY=:0.0, it's OK. Now we test to start xlogo and the return the error can't open display :0.0. I try to change the display to localhost:0.0, to the host name, etc... with the same result. I think it's possible a problem with the security of the server.
          We use Suse SLES 10.
          • SystemAdmin
            SystemAdmin
            90 Posts
            ACCEPTED ANSWER

            Re: X-Window Application

            ‏2007-05-08T18:51:14Z  in response to ramso
            Hi,

            It looks like some environment setup issue since I don't see the error message when I setup my environment properly. I would like to discuss with you.

            Here is my email id. vijir@us.ibm.com

            Please email me your phone number and email id at vijir@us.ibm.com.

            Thanks,
            Viji
  • SystemAdmin
    SystemAdmin
    90 Posts
    ACCEPTED ANSWER

    Re: X-Window Application

    ‏2007-10-09T14:23:15Z  in response to ramso
    We hit a similar problem recently..
    And here's what we did to get it working as an example.
    Can't tell if this was the problem you originally had...

    We start from a standard Linux (ubuntu) desktop...

    This worked out of the box..
    ssh -X root@power5.austin.ibm.com
    xclock &

    This did not:
    ssh -X root@power5.austin.ibm.com
    cd /i386
    runx86
    xclock &

    What's missing is the .Xauthority file in the /root directory in the translated world - ie: /i386/root/.Xauthority

    So...

    As root in the native mode, we just create a link for the file...

    ssh -X root@power5.austin.ibm.com
    cd /i386/root
    ln -s /root/.Xauthority .Xauthority
    exit

    In the future, the latter example from above should now work.

    ssh -X root@power5.austin.ibm.com
    cd /i386
    runx86
    xclock &