Mailing List Archive: wrong DISPLAY variable

wrong DISPLAY variable

Dec 7, 2010, 10:33 AM

Post #1 of 3 (4604 views)

iqbala@jp2 { ~ }$ ssh -Y hlr-brixuat-01.example.net.
Password:
Last login: Tue Dec 7 17:33:46 2010 from jp2.example.net
[iqbala@hlr-brixuat-01 ~]$ xterm
_X11TransSocketINETConnect() can't get address for hostname:6000: Name
or service not known
xterm Xt error: Can't open display: hostname:0.0

[iqbala@hlr-brixuat-01 ~]$ echo $DISPLAY
hostname:0.0

[iqbala@hlr-brixuat-01 ~]$ env | grep DISPLAY
DISPLAY=hostname:0.0

[iqbala@hlr-brixuat-01 ~]$ DISPLAY=:0.0 xterm
xterm Xt error: Can't open display: :0.0

so DISPLAY id is wrong.

[iqbala@hlr-brixuat-01 ~]$ xauth list $DISPLAY
xauth: (argv):1: bad display name "hostname:0.0" in "list" command

so I run xauth list to guess the correct DISPLAY id

[iqbala@hlr-brixuat-01 ~]$ xauth list
hlr-brixuat-01.ip.qwest.net/unix:10 MIT-MAGIC-COOKIE-1
6e28736cb0f1227240fb9cd0ee304ca8
hlr-brixuat-01.ip.qwest.net/unix:12 MIT-MAGIC-COOKIE-1
f67286cba96bf92053290c367af9c1c3
hlr-brixuat-01.ip.qwest.net/unix:11 MIT-MAGIC-COOKIE-1
6687e7e136b618bbddca53ee7a10cba7
hlr-brixuat-01.ip.qwest.net/unix:13 MIT-MAGIC-COOKIE-1
b8821e6e537c7c9803342f7aa04cea76

so lets pick DISPLAY id as 12.0

[iqbala@hlr-brixuat-01 ~]$ DISPLAY=:12.0 xterm
X connection to localhost:12.0 broken (explicit kill or server shutdown).

looks like I picked the wrong DISPLAY id. lets pick the next one, which is 13.0

[iqbala@hlr-brixuat-01 ~]$ DISPLAY=:13.0 xterm

Yes! this time it worked.

Why do I have to pick a DISPLAY id? shouldn't xterm pick the correct
DISPLAY id already?

I am running OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 on
Red Hat Enterprise Linux Server release 5.5 (Tikanga)

Any suggestion on fix is appreciated.

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Re: wrong DISPLAY variable [ In reply to ]

dtucker at zip

Dec 7, 2010, 12:55 PM

Post #2 of 3 (4536 views)

Permalink

On 8/12/10 5:33 AM, Asif Iqbal wrote:
> iqbala@jp2 { ~ }$ ssh -Y hlr-brixuat-01.example.net.
> Password:
> Last login: Tue Dec 7 17:33:46 2010 from jp2.example.net
> [iqbala@hlr-brixuat-01 ~]$ xterm
> _X11TransSocketINETConnect() can't get address for hostname:6000: Name
> or service not known
> xterm Xt error: Can't open display: hostname:0.0

Most likely something in your shell startup scripts is (re)setting
$DISPLAY to the wrong value. sshd will set display numbers of 10 and up
(by default, this can be changed in sshd_config via X11DisplayOffset).

--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

Re: wrong DISPLAY variable [ In reply to ]

vadud3 at gmail

Dec 7, 2010, 2:34 PM

Post #3 of 3 (4526 views)

Permalink

On Tue, Dec 7, 2010 at 3:55 PM, Darren Tucker <dtucker@zip.com.au> wrote:
> On 8/12/10 5:33 AM, Asif Iqbal wrote:
>>
>> iqbala@jp2 { ~ }$ ssh -Y hlr-brixuat-01.example.net.
>> Password:
>> Last login: Tue Dec 7 17:33:46 2010 from jp2.example.net
>> [iqbala@hlr-brixuat-01 ~]$ xterm
>> _X11TransSocketINETConnect() can't get address for hostname:6000: Name
>> or service not known
>> xterm Xt error: Can't open display: hostname:0.0
>
> Most likely something in your shell startup scripts is (re)setting $DISPLAY
> to the wrong value. sshd will set display numbers of 10 and up (by default,
> this can be changed in sshd_config via X11DisplayOffset).

Thanks a lot for the pointer. That is exactly what happened.

There was this line in the .bash_profile. Not sure how it got there.

DISPLAY=hostname:0.0; export DISPLAY

I commented it out. Now its all good. Thanks a lot again

>
> --
> Darren Tucker (dtucker at zip.com.au)
> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
> Good judgement comes with experience. Unfortunately, the experience
> usually comes from bad judgement.
>

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?