Re: Can't open display: hostname:0.0



On Thu, Apr 26, 2007 at 02:39:30PM -0700, Dave Martini wrote:
# xclock
Error: Can't open display: raider4:0.0

What will cause the above error? I'm logged into a remote machine from
my own RHEL 4 box.
I also typed xhost +hostname from my RHEL 4 box to allow the other
machine to display on my server. My DISPLAY environment variable is the
correct name of my RHEL 4 box.

No firewall/iptables rules getting in the way?

Ray

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list



Relevant Pages

  • Cant open display: hostname:0.0
    ... Error: Can't open display: raider4:0.0 ... I'm logged into a remote machine from my own RHEL 4 box. ... I also typed xhost +hostname from my RHEL 4 box to allow the other machine to display on my server. ...
    (RedHat)
  • Re: Cant open display: hostname:0.0
    ... I also typed xhost +hostname from my RHEL 4 box to allow the other machine to display on my server. ... Unless you've reconfigured your X startup the X server won't be listening for network connections. ...
    (RedHat)
  • Re: Cant open display: hostname:0.0
    ... Dave Martini wrote: ... I'm logged into a remote machine from my own RHEL 4 box. ... I also typed xhost +hostname from my RHEL 4 box to allow the other machine to display on my server. ...
    (RedHat)
  • Re: Tkinter(2)
    ... from Tkinter import Label ... widget = Label ... no display name and no $DISPLAY environment ... This error usually happens when you're logged in on a remote machine, and you didn't tell the remote machine where you wanted to display the windows you open. ...
    (comp.lang.python)
  • Re: setting up console boot
    ... connection first. ... > specific null modem USB2Serial adapter, odds are you need a null modem ... don't see that I have login to the remote machine with the shell display. ...
    (comp.unix.bsd.freebsd.misc)