Re: Horrible X11 Problems on OS X (iBook)
Re: Horrible X11 Problems on OS X (iBook)
- Subject: Re: Horrible X11 Problems on OS X (iBook)
- From: Vernon Williams <email@hidden>
- Date: Thu, 23 Dec 2004 20:09:03 -0600
Thursday, December 23, 2004, 7:45pm
I have been following this thread, and I would be curious about several
things.
First, in the problematic xterm, can you enter any number of commands
okay?
Can you enter some that can take keyboard input, like cat? To create a
file, say.
If so, try something like touch myfile.dat or ls -l > dir.prt
or the like. Then
from Terminal, which I think you said works, see if the file is created
or that the
directory listing is correct. If so, then the commands are working,
but somehow
standard output is being redirected somewhere, effectively to
/dev/null. How that
could happen, I do not know. This way you could at least see what
environment
variables are being set, by redirecting the info to a file and looking
at the file,
as in echo $PATH > path.prt. You could also use the which command to
check which executables are actually being run, such as which xterm >
xterm.prt.
If you can run xterm from Terminal, as xterm & , then it is probably
not a problem
with xterm per se.
You might try running various shells in your problematic xterm and see
if you
can successfully run commands in any of them. That might tell you if
it is a
problem in a configuration file for a particular shell.
Just in case your X11 on your install CD is glitched slightly (these
things do
happen occasionally), you might try downloading the copy from the Apple
web site (what I did when I installed on my new G5 tower recently).
Vernon Williams
On Dec 23, 2004, at 6:22 AM, Douglas Stetner wrote:
On 23/12/04 at 11:53 (+0100), Martin Costabel <email@hidden>
wrote:
Stephen Sebeny wrote: []
So, thanks again to everyone who responded, its truly appreciated.
And hopefully given the details above someone out there will know for
sure how to lock-in the effect of the DISPLAY=:0.0 statement and make
its effect permanent. (fingers-crossed!) Thanks!
...
...
Otherwise, your problem remains mysterious. You more or less
demonstrated that it can only be a hardware problem, but I cannot
imagine one that would give this strange behavior.
I have been watching this thread go by, racking my brain trying to
remember what
causes this problem. I *have* seen it before, it is NOT hardware, and
I don't
think it is X11, I think it is a shell config problem.
I cannot remember if it is a pty thing or some stty setting, but it is
definitely a shell thing. If it was X11 that was futzed, then an 'ls'
should
work. If it was X11, the 'set DISPLAY and run a command from the
terminal'
would not work.
Basically the shell has gone brain dead due to an error somewhere in
the config
files. I would look for non-matched quotes, bad stty settings etc.
In fact my
first step in trouble shooting this would be to move aside all
personal 'dot'
files from a vanilla user and see if it still occurs.
As I said, I have seen this before, but I will be damned if I can put
my finger
on it now....
The prompt setting seems to ring a bell as well....
Hope you find it soon...
--
Douglas Stetner stetner AT stetner DOT
org
There are two major products that come out of Berkeley: LSD and UNIX.
We
don't believe this to be a coincidence. --Jeremy S. Anderson
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden