Re: MATLAB R2007a, Leopard and X11
Re: MATLAB R2007a, Leopard and X11
- Subject: Re: MATLAB R2007a, Leopard and X11
- From: Leslie Wright <email@hidden>
- Date: Sun, 11 Nov 2007 12:53:27 -0500
Prof Hesford, the only X11 app I use right now is the OpenOffice suite.
There are some connection issues with it, but not as serious as your
experiences with Matlab. If OpenOffice is opened without X11 being up
and running already, it will poke along and eventually present a message
box advising "Command timed out". I clear it, and OpenOffice opens normally.
The only workaround I have found for this annoyance is launching X11
first. For convenience I have added /Applications/Utilities/X11.app to
my Login Items at System Preferences > Accounts. As you know, launching
X11 this way flashes up xterm whether I want it or not! But it works. I
have a new iMac with 4GB of RAM so having X11 chugging in the background
is no stress on the machine for the most part.
Mr. Byer's Xquartz upgrades have steadily improved the performance of
X11 under Leopard and I am hoping that connection issues like this will
yield to his hard work in the days to come. I am pretty sure he and
Apple are aware of it.
This doesn't solve your problem, but I hope the commiseration is
encouraging.
Les
Andrew J. Hesford wrote:
I've noticed an issue with MATLAB R14, MATLAB R2007a, Leopard and the
new X11. The problem occurs with both the shipping version of the
Xquartz server, and version 1.2a8 from the XDarwin wiki. I've also
tried upgrading libX11, but that doesn't make a difference. I have a
1.83 GHz Core Duo iMac with 1 GB RAM and the Intel GMA 950 (one of the
original education models).
MATLAB tends to be fickle when starting with X11 in Leopard. If I
start the program once, it requests an X11 connection, and launchd
starts the X server. As long as I keep the X server running, I can
quit and relaunch MATLAB, and everything works fine.
However, if I kill the server (after quitting MATLAB) and relaunch
MATLAB, I run into problems. Launchd will restart the X server, but
the X server will not respond to any connection attempts. This occurs
whether the connection attempts come from the local or a remote
client, and whether or not MATLAB is run on the local or a remote
client. MATLAB will hang, failing to start because the X server is
responding. Xterm similarly hangs, so I get no window when I attempt
to start it.
At this point, if I kill all the clients and then kill the X server
(by selecting the dock icon and pressing Command-Q), launchd will
immediately relaunch the server. If I attempt another client connect
(such as starting an Xterm), it will again hang.
To get back functionality, I have to kill all clients, and kill the
server. When it immediately restarts, I have to kill it again. After
that, it appears that launchd does not attempt to restart the server.
I believe it was attempting to restart because it has a buffered
request from a client. Killing it the second time clears the buffer,
and launchd no longer things anything is trying to connect. However, I
still cannot start MATLAB, or the server will get hosed again. If I
kill X11 until it has stopped trying to respawn and start an Xterm, it
will open properly. Then, once the server is running, I can run MATLAB
again.
After all the tests, it seems like the cause is starting the X server
in a normal, responsive state, killing the server, and then attempting
to start MATLAB. While the server starts, it appears to hang. However,
if I get the server to first respond with something like an Xterm, I
can start MATLAB as long as the server is already running.
Thanks,
Andrew Hesford
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden