Re: Readline initialization in .bash_profile -> Xquartz crash
Re: Readline initialization in .bash_profile -> Xquartz crash
- Subject: Re: Readline initialization in .bash_profile -> Xquartz crash
- From: Jeremy Huddleston <email@hidden>
- Date: Tue, 19 Feb 2008 01:25:38 -0800
Sorry for being unclear. I really don't need to see what your
xdpyinfo output is. I just wanted you to use a command other than
'xterm' to start X because xterm is envoked from many different places.
What I wanted was for you to set app_to_run to /usr/bin/true, so it's
no longer xterm, and use xdpyinfo (or any other X application) from
the terminal to start X (so that's not xterm). The error message in
your log is puzzling to me, so I'm just trying to figure some things
out...
What I want to see is the output to Console.app that results from you
running xdpyinfo (or glxinfo, glxgears, xeyes, whatever... just not
xterm).
Sorry for the confusion, and hopefully we can figure this out tomorrow .
Jeremy
On Feb 19, 2008, at 01:02, Knut Arild Lisæter wrote:
Hi Jeremy,
I know its bizarre, but thats what seems to happen... There is no
crash log, because X doesnt really seem to "crash" (bad phrasing by
me), it starts up, dumps the message to system.log and quits.
If I take the output from xdpyinfo it's the same in both cases (when
I keep the offending command in .bash_profile and when I dont). The
difference is that in one case X quits right after xdpyinfo is
finished - in the other X is still running.
Just to be clear - this problem happens when I start up X. I have no
X running and type "xterm" in terminal.
In any case I have attached the output from xdpyinfo at the end of
this mail.
-Knut
On Feb 19, 2008, at 9:41 AM, Jeremy Huddleston wrote:
I don't see how an invalid command in your .bashrc could cause X to
crash. That is just bizzare... do you have the crash log?
What happens when you do the following from within Terminal.app:
defaults write org.x.X11 app_to_run /usr/bin/true
xdpyinfo
Can you please provide the entire output of your log that results
from running xdpyinfo above.
Thanks,
Jeremy
On Feb 19, 2008, at 24:30, Knut Arild Lisæter wrote:
No custom .xinitrc here... Any other configuration files that
could be causing this?
I have the newest Xquartz, and the problem is still there.
--Knut
On Feb 18, 2008, at 8:28 PM, Jeremy Huddleston wrote:
Nope... it works fine for me.
Do you have a custom ~/.xinitrc? If so, can you please move it
aside and try again?
On Feb 18, 2008, at 02:33, Knut Arild Lisæter wrote:
Hi,
I've had some problems upgrading to the newest versions of
Xquartz, due to the presence of "readline" initialization in my
bash_profile. The offending command was
set bell-style visible
which caused Xquartz to crash with the error message :
xterm: fatal IO error 32 (Broken pipe) or KillClient on X
server "/tmp/launch-8C8kTO/:0"
and /var/log/system.log says:
xterm: bad command line option "xterm"
On my system this behaviour is consistent (adding the above
command in .bash_profile, quitting X11 and restarting with
"xterm" in terminal.app then Xquartz will crash). It would be
nice if someone else can confirm this as well - I have seen
other people have had similar problems, for instance: http://forums.macosxhints.com/showthread.php?p=445567
.
As I understand (now) the proper place for these commands are in
the ~/.inputrc file, but is it possible to avoid Xquartz
crashing like this? Or maybe add a tip to the FAQ?
I have attached the system.log output below
Best Regards,
Knut Liseter
<xdpyinfo.out>
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden