HPTerm in CDE

[Jeff Miller - 1]

I am using Exceed 10 on my PC to run X Windows on a RP5470 running HPUX 11.11.

Everything is running great except that I cannot start up an hpterm (xterm and dtterm work fine).

When I try to start up an hpterm, I get the error:

Error: Can't open display: usel4383.us.essilor.pvt:0.0
Error: Couldn't find per display information

This issue is not an "xhost" or a DISPLAY issue as I can start up an xterm and a dtterm window in the same window that I try to start up the hpterm.

I seem to recollect that there is a hpterm bug buried somewhere in CDE that prevents this from happening.

Can anyone out there help me jog my memory??

Thanks!!

[Peter Godron]

Jeff,
one thing I could find on this was:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=238940

Hope this helps with your investigation

[Jeff Miller - 1]

Good suggestion!!

I forgot about "dr_dt". I ran this utility, but it didn't point out any errors and the warnings were for minor permission issues (ie: permissions on "/etc/hosts" were 644 versus 444).

Anyone else out there have any ideas??

Thanks

[Alex Glennie · Accepted solution]

Can you run hpterm & from within the working dtterm or xterm windows ... does it work.

Are you just running the terminals as individual clients or within CDE ?

If individually what command line options are you using (if any) within exceed ?

Are you 100 % certain name resolution is not an issue or inconsistent here ?

Can you enable Exceed debugging/logging ?

No other ideas at present.

[Jeff Miller - 1]

I am running these terminals out of the CDE environment. When I start up an XTERM or a DTTERM, I can start up xterms, dtterms galore. If I try to crank up an HPTERM from a DTTERM or an XTERM, I get the same error as before. If I set the DISPLAY variable (which I should not have to do), then everything fires up without issue...

Something somewhere is trashing the DISPLAY environment for HPTERM.

I will setup logging for Exceed and post it or let you know if the data within the log file is not worth posting...

Thanks!!

[Jeff Miller - 1]

Attached is the Exceed log file. Sorry for the delay in getting this posted. The actual error associated with this issue is located at the bottom of the log file and states:

Connection read error at 73157

I did a GOOGLE search on this error, but did not find anything of relevance.

[Alex Glennie]

Thoughts ....

I don't *think* this is likely to be fonts, despite their abundance in the log file or the numeric error, though I also failed to find it's meaning. Does it occur when you don't open an hpterm.

I suspect based on your earlier results that the DISPLAY is linked in here somehow.

Are any other users affected here, have you customised .dtprofile or .profile (or similar) for your user ?

What if : you add DISPLAY=???.???.???.??:0 in $HOME/.profile and run from dtterm ->

hpterm -ls &

A thought ... try disabling user based Xauthority ....

resource = Dtlogin*Authorise : True/False

see /usr/dt/config/Xaccess

restart CDE any better ?

one other idea ....

use tusc/trace to trace some of the processes involved here eg dtlogin, or a dtterm and run hpterm from within maybe ?

eg

tusc -fl -o/tmp/X-tusc.log -T "%T" -v -p

Also you could try adding set -x in .dtprofile and logout, log back in,reproduce problem and check $HOME/.dt/error.log and start.log

[TwoProc]

From everything written thus far...
The easiest explanation that I can come up with is that it sounds to me like someone renamed the hpterm executable, put a script in its place, in which the DISPLAY variable was set to their own PC/workstation/etc.

Can you give us the output of:
> which hpterm
and
> file `which hpterm`

I'd like to see at least this possible cause ruled out.

[Jeff Miller - 1]

I have a few minutes before a meeting, thus I thought I would reply to some of the requests of Alex and John...

[useo0020@jemiller]: which hpterm
/usr/bin/X11/hpterm
[useo0020@jemiller]: file `which hpterm`
/usr/bin/X11/hpterm: s800 shared executable dynamically linked -not stripped

The font errors occur when I first start up CDE. The "Connection read error..." is the only message that pops up in the log file when I try to start an HPTERM.

I will try the rest of your suggestions later today...

Thanks!!

[TwoProc]

OK Jeff - I can see that it's not a script overrun by another admin... Thanks.

[Jeff Miller - 1]

The issue ended up being a DNS issue that only affected HPTERM. Alex's first post asked me to double check this. I guess I should have checked a bit closer...

I am using my laptop (running XP Pro) to run CDE on a second monitor. My laptop has two network ports (wired and wireless). When I executed an NSLOOKUP against my laptop hostname, DNS returned both IP addresses. On the HPUX server that I am using to run the full CDE environment, I have the "/etc/nsswitch.conf" looking at the "/etc/hosts" file first and then DNS, thus I added the wired IP address to the hosts file, restarted the CDE Workspace Manager and HPTERM fired up without problems...

VERY strange that this would only happen to HPTERM. Oh well, thanks to all who posted!!