02-24-2009 03:54 AM
When I type xclock at the shell prompt there no xclock display
In fact any X application does not display on my screen. I have Exceed server running on my laptop from I login via ssh to my TRU64 Unix server.
All X applications use to work 7 months ago but recently they do not display anything.
Any help would appreciated.
02-24-2009 09:35 AM
> ssh session
Great. Now if I knew the names of any of the
computers involved here, ...
Or were you hoping for help from some psychic
who already knows everything about your
02-25-2009 07:06 AM
>lysithea$ echo $DISPLAY
So when logged in into lysithea, your $DISPLAY pointt to lysithea as outputdevice.
On the lysithea console the clock may appear and not on your laptop!
=> correct setting $DISPLAY in $HOME/.profile or $HOME/.dtprofile
02-25-2009 10:58 AM
So on the main Lysithea console the xclock appears fine but not on my laptop.
There is a firewall between my laptop and Lysithea and I can login to Lysithea with ssh after authenticating to the firewall. We have 3 other servers running the same version of the Tru64 Unix 5.1b and all 3 servers are behind the firewall and xclock appears on my laptop for each of the 3 systems using ssh.
I have not changed any settings on ssh apart from enabelling X tunnelling in ssh for Lysithea.
I have noticed if I type xclock & on my laptop the xclock application seems to be "killed" immediately without any errors.
There are no xclock processes after I type xclock & running in the backgroundd.
I have tried using Exceed and Xming on my laptop as the X server but xclock still does not appear on my laptop. The last time xclock worked on my laptop was 8 or 9 months ago. We need to install Oracle which uses a GUI but we cannot proceed as it uses X server for the installation from a laptop.
I've looked at the sshd settings all looks fine to me.
I understand its a difficult to help me without giving you full details of the current environment.
I dont know where else to look.
02-25-2009 11:21 AM
> I have set the X11 tunnelling with my ssh
Apparently you haven't. Or perhaps your
shell start-up script ("~/.profile"?) sets
DISPLAY to this value after the SSH stuff
sets it to what it should be.
02-27-2009 07:41 AM
Anyway, it can also be a permission problem (OK, I do not think so, but ...) or env problem (PATH).
Error message may help.
02-27-2009 09:25 AM
If I type xclock only, nothing happens. I get returned to the shell prompt straight away without any error message. It is very odd there is no error message after I type xclock. If I run "xclock &" I did not see any xclock process when I use "ps -eaf | grep -i xclock" to check for it. Normally, you would see background process of xclock.
See output below of xclock command.
lysithea$ xclock &
 + Done xclock &
As I mentioned if I run xclock from the main Tru64 Unix console I see it appear on the screen.
I will reboot the server which been running for 448 days. May be rebooting may fix it.
The server was fully patched to patch kit 6 almost two years ago.
02-27-2009 02:43 PM
> wrong host:server.screen?
Good point. Perhaps black really is white,
and up really is down. But I doubt it.
The info from the questioner is vague and
incomplete, but, as I understand / assume /
conjecture what's happening here, lysithea =
lysithea.mdx.ac.uk, and that's the Tru64
system, not the laptop with the X server.
So, I conclude that any DISPLAY which uses
lysithea:0 for its host:server part must be
I don't have a laptop running Exceed, but I
do have a Sun Solaris workstation, and when
I use "ssh -X" to connect from it to another
system, I get results like the following.
To a Tru64 system:
sol> ssh -X urtx
HP Tru64 UNIX V5.1B (Rev. 2650); Mon Feb 19 11:57:07 CST 2007
urtx> echo $DISPLAY
To an HP-UX (11.11) system:
sol> ssh -X dy
Value of TERM has been set to "xterm".
dy $ echo $DISPLAY
where 10.0.0.39 is the IP address of "dy",
the HP-UX system.
So, I conclude that a typical sshd sets up
a virtual X server at server_host:10.0 (and
it even seems to work around here).
The questioner reported that his DISPLAY was
"lysithea.mdx.ac.uk:0.0". To me, this does
not appear to be consistent with his claim
that he had "set the X11 tunnelling with
[his] ssh session". Based on the results of
my tests, I'd expect it to be something like
I've tried to guess who set DISPLAY to the
reported value, but so far I've learned
nothing about it. My guess is still that
it's something in the user's shell start-up
script(s), but my psychic powers are too weak
to tell me more.
I have code in my own "~/.profile" which
looks at the output of "who am i", and uses
it to set DISPLAY, but it's inside a test
if [ -z "$DISPLAY" ]; then
so, if someone else (like, say, sshd) sets
DISPLAY for me, I don't whack its (good)
DISPLAY definition with my (bad) DISPLAY
> May be rebooting may fix it.
The X Window System is not Microsoft Windows,
so I doubt it.
03-02-2009 07:49 AM
The xclock file in the /usr/bin/X11 directory was empty i.e. zero blocks and the creation date of the xclock file was 31st Jan 2008.
I dont know how xclock file got to be in
I've copied xclock file from another Tru64 unix system to this one.
Now xclock appears on my laptop fine.
Thank you to everyone for their help.