topic Re: Xterm and Dterm ? in Operating System - HP-UX

Xterm and Dterm ?

Patrick H Hughes — Mon, 10 Sep 2001 18:17:06 GMT

After logging into desktop and opening a dterm window I get nothing but bogus characters returned. Any additional dterm windows open render the same results. I did a telnet session from a workstation and also received bogus characters in a xterm window. Thus far I have restored the /usr /h/COTS /h/COE and the profile and login files under the / directory. In single user mode everything appears normal. Any idea or suggestions on what to try next?

Thanks,

Patrick H. Hughes
SPAWAR Systems Center Chesapeake, VA
phughes@scn.spawar.navy.mil

Re: Xterm and Dterm ?

Runar Jørgensen — Tue, 11 Sep 2001 11:47:12 GMT

Looks like you're having font problems. Check out
$HOME/.dt/errorlog
and /var/dt/Xerrors. Make sure LANG and is set to something reasonable, and verify if you use Roman-8 character set or
an ISO set.

Re: Xterm and Dterm ?

Wodisch — Tue, 11 Sep 2001 12:00:19 GMT

Hello Patrick,

can you login on your console and run something like

UNIX95=x ps -efH

there, while you see the "bogus" characters in that
dtterm or xterm?

Then look "below" the line for the dtterm/xterm:
There will be line for the "shell", and perhaps there
are even more lines, all indented to the right...
What are those lines showing (i.e. what processes are
running)?

Is this true for all users, all terminals, all networked
sessions (telnet, rlogin, remsh, X-Windows failsafe
session, X-Windows CDE session, console terminal)?

HTH,
Wodisch

Re: Xterm and Dterm ?

Charles Slivkoff — Tue, 11 Sep 2001 19:22:02 GMT

Does text appear normal when you login to CDE? Do the Dtterm menus look normal? Have you tried specifying a different font via the menu? Have you tried a "failsafe" session? What about the CDE text editor "dtpad" from the front-panel? Do you login on the console of the system directly, or via an X terminal, PC, etc?

In the CDE "Application Manager" you will find an icon for "xwd" which will let you take a window dump and save to a file. Use this to grab a shot of the dtterm/xterm display and we'll probably be able to offer additional suggestions.

Re: Xterm and Dterm ?

Patrick H Hughes — Thu, 13 Sep 2001 18:24:19 GMT

Further research reveals that this begins to happen when you issue a l, ls, ls -l command from the / directory. You can change out of the / directory, and the l commands work fine but if you change back to the root directory and issue a l command then the garble starts.
All other commands while in the root directory appear to work correctly.

Re: Xterm and Dterm ?

Patrick H Hughes — Thu, 13 Sep 2001 18:28:15 GMT

The environment appears to be fine. Doesn't matter which user is logged in, the same results occur.

Re: Xterm and Dterm ?

linuxfan — Thu, 13 Sep 2001 21:15:04 GMT

Hi Patrick,

Can you check if "ls" is an alias. Do a
"type ls"

and since you are saying this is happening to all users, check the /etc/profile and see if you are aliasing ls there.

Did you see anything in the errorlogs?

-Regards
Ramesh

Re: Xterm and Dterm ?

Charles Slivkoff — Fri, 14 Sep 2001 02:59:57 GMT

OK, I think I figure this one out. Try "ls -bi". I suspect you will see one or more files with \0nnn in their names. This implies that one or more file names have been created with characters that are not normally printable.

Using the inode listed (from "-i") and "find", you can rename these file with something like:

let count=0

for file in $(find / -xdev -inum insertinodenumberhere )

do

mv -i $file /tmp/badfile.$count

let count++

done

Re: Xterm and Dterm ?

Charles Slivkoff — Fri, 14 Sep 2001 03:04:18 GMT

You've got one or more files with non-printable characters in their names. Try:

ls -ib

This will display the non-printables as octal values.

Then, using the inode number (from the "-i" option) for each file, you can move these to /tmp & rename them using something like:

find / -xdev -inum INODE -exec mv -i {} /tmp/badfile \;

Re: Xterm and Dterm ?

Stefan Farrelly — Fri, 14 Sep 2001 06:18:26 GMT

I think your home directories .dt subdir is corrupt. Simply
rm -rf $HOME/.dt
and then log into the desktop again and it will be recreated.