Unable to open display issue - Xwindows

This is a discussion on Unable to open display issue - Xwindows ; I just installed Slackware 10. A fresh, clean install. My X version: Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.7 Build Operating System: Linux 2.4.26 i686 [ELF] Current Operating System: Linux tron 2.4.26 #21 Mon ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Unable to open display issue

  1. Unable to open display issue

    I just installed Slackware 10. A fresh, clean install. My X version:

    Release Date: 18 December 2003
    X Protocol Version 11, Revision 0, Release 6.7
    Build Operating System: Linux 2.4.26 i686 [ELF]
    Current Operating System: Linux tron 2.4.26 #21 Mon Jun 14 19:17:44
    PDT 2004 i686
    Build Date: 05 June 2004
    Before reporting problems, check http://wiki.X.Org
    to make sure that you have the latest version.
    Module Loader present

    Now whenever I login to another machine and forward a display it
    continues to say "Unable to open display".

    On my local machine I set xhost + (yes, I know that's a security risk,
    this is for troubleshooting)
    On the remote server I do export DISPLAY to my_local_ip:0.0.
    I've also tried logging in to the remote server using -X.

    None of that fixes the problem. The remote server hasn't changed, only
    my local machine.

    I don't know what else to do. Can anyone give me pointers on what to
    check?

    --Matt

  2. Re: Unable to open display issue

    Matthew Sims wrote:
    >I just installed Slackware 10. A fresh, clean install. My X version:
    >
    >Release Date: 18 December 2003
    >X Protocol Version 11, Revision 0, Release 6.7
    >Build Operating System: Linux 2.4.26 i686 [ELF]
    >Current Operating System: Linux tron 2.4.26 #21 Mon Jun 14 19:17:44
    >PDT 2004 i686
    >Build Date: 05 June 2004
    > Before reporting problems, check http://wiki.X.Org
    > to make sure that you have the latest version.
    >Module Loader present
    >
    >Now whenever I login to another machine and forward a display it
    >continues to say "Unable to open display".
    >
    >On my local machine I set xhost + (yes, I know that's a security risk,
    >this is for troubleshooting)
    >On the remote server I do export DISPLAY to my_local_ip:0.0.
    >I've also tried logging in to the remote server using -X.
    >
    >None of that fixes the problem. The remote server hasn't changed, only
    >my local machine.
    >
    >I don't know what else to do. Can anyone give me pointers on what to
    >check?


    Many newer distros start the X server with -nolisten tcp, which is
    something you can easily check with ps.


  3. Re: Unable to open display issue

    kbr@pangea.ca (Kip Rugger) wrote in message news:...
    > Matthew Sims wrote:
    > >I just installed Slackware 10. A fresh, clean install. My X version:
    > >
    > >Release Date: 18 December 2003
    > >X Protocol Version 11, Revision 0, Release 6.7
    > >Build Operating System: Linux 2.4.26 i686 [ELF]
    > >Current Operating System: Linux tron 2.4.26 #21 Mon Jun 14 19:17:44
    > >PDT 2004 i686
    > >Build Date: 05 June 2004
    > > Before reporting problems, check http://wiki.X.Org
    > > to make sure that you have the latest version.
    > >Module Loader present
    > >
    > >Now whenever I login to another machine and forward a display it
    > >continues to say "Unable to open display".
    > >
    > >On my local machine I set xhost + (yes, I know that's a security risk,
    > >this is for troubleshooting)
    > >On the remote server I do export DISPLAY to my_local_ip:0.0.
    > >I've also tried logging in to the remote server using -X.
    > >
    > >None of that fixes the problem. The remote server hasn't changed, only
    > >my local machine.
    > >
    > >I don't know what else to do. Can anyone give me pointers on what to
    > >check?

    >
    > Many newer distros start the X server with -nolisten tcp, which is
    > something you can easily check with ps.



    I did make some progress with my issue. I ended up recreating the
    ..Xauthority file and it helped. I can forward over
    /usr/openwin/bin/xlogo and admintool. But I can't forward a
    third-party application. I get this error now:

    X Error of failed request: BadDrawable (invalid Pixmap or Window
    parameter)
    Major opcode of failed request: 73 (X_GetImage)
    Resource id in failed request: 0x40
    Serial number of failed request: 132
    Current serial number in output stream: 132

    From what I've read around the internet, I get the feeling that the
    app is having issues drawing itself on my local desktop due to a
    possible naming problem or resolution issue? I couldn't find anything
    a little more specific.

    --Matt

  4. Re: Unable to open display issue

    Matthew Sims wrote:
    >
    >I did make some progress with my issue. I ended up recreating the
    >.Xauthority file and it helped. I can forward over
    >/usr/openwin/bin/xlogo and admintool. But I can't forward a
    >third-party application. I get this error now:
    >
    >X Error of failed request: BadDrawable (invalid Pixmap or Window
    >parameter)
    > Major opcode of failed request: 73 (X_GetImage)
    > Resource id in failed request: 0x40
    > Serial number of failed request: 132
    > Current serial number in output stream: 132
    >
    >From what I've read around the internet, I get the feeling that the
    >app is having issues drawing itself on my local desktop due to a
    >possible naming problem or resolution issue? I couldn't find anything
    >a little more specific.
    >
    >--Matt


    Looking at the error, your app is trying to *read* the display, and
    because the resource id has a client field of 0, I would guess that
    the app is trying to look at the root window.

    My guess is that this is being disallowed as a security breach.

    This will not happen if you use ssh properly, or if you use xauth
    to generate a *trusted* authorization and properly install that.


  5. Re: Unable to open display issue

    matt@killermookie.org (Matthew Sims) wrote in message news:<1e963607.0407142224.169b68c4@posting.google.com>...
    > kbr@pangea.ca (Kip Rugger) wrote in message news:...
    > > Matthew Sims wrote:
    > > >I just installed Slackware 10. A fresh, clean install. My X version:
    > > >
    > > >Release Date: 18 December 2003
    > > >X Protocol Version 11, Revision 0, Release 6.7
    > > >Build Operating System: Linux 2.4.26 i686 [ELF]
    > > >Current Operating System: Linux tron 2.4.26 #21 Mon Jun 14 19:17:44
    > > >PDT 2004 i686
    > > >Build Date: 05 June 2004
    > > > Before reporting problems, check http://wiki.X.Org
    > > > to make sure that you have the latest version.
    > > >Module Loader present
    > > >
    > > >Now whenever I login to another machine and forward a display it
    > > >continues to say "Unable to open display".
    > > >
    > > >On my local machine I set xhost + (yes, I know that's a security risk,
    > > >this is for troubleshooting)
    > > >On the remote server I do export DISPLAY to my_local_ip:0.0.
    > > >I've also tried logging in to the remote server using -X.
    > > >
    > > >None of that fixes the problem. The remote server hasn't changed, only
    > > >my local machine.
    > > >
    > > >I don't know what else to do. Can anyone give me pointers on what to
    > > >check?

    > >
    > > Many newer distros start the X server with -nolisten tcp, which is
    > > something you can easily check with ps.

    >
    >
    > I did make some progress with my issue. I ended up recreating the
    > .Xauthority file and it helped. I can forward over
    > /usr/openwin/bin/xlogo and admintool. But I can't forward a
    > third-party application. I get this error now:
    >
    > X Error of failed request: BadDrawable (invalid Pixmap or Window
    > parameter)
    > Major opcode of failed request: 73 (X_GetImage)
    > Resource id in failed request: 0x40
    > Serial number of failed request: 132
    > Current serial number in output stream: 132
    >
    > From what I've read around the internet, I get the feeling that the
    > app is having issues drawing itself on my local desktop due to a
    > possible naming problem or resolution issue? I couldn't find anything
    > a little more specific.
    >
    > --Matt


    I resolved it. I need to have a -Y when sshing:

    ssh -X -Y hostname

    --Matt

+ Reply to Thread