Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- Subject: Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues
- From: Jeremy Huddleston <email@hidden>
- Date: Thu, 25 Sep 2008 09:05:18 -0700
On Sep 25, 2008, at 00:48, Dave Ray wrote:
The X11 FAQ page does start out to say "Don't like launchd? Disable
it." You might want to update the FAQ if launchd is important, or at
least explain those issues in that section of the FAQ.
You're right. That FAQ is a bit dated. I'll work on revising it this
weekend if nobody else gets to it (it should be world editable BTW).
I didn't realize the runaway condition was of interest to anyone, I
thought it was specific to my setup. Let me describe what i remember
about it and how I made it go away.
Before I upgraded to 10.5.5, my X11 environment was stable, I used
X11.app to launch it. I was using the Enlightenment WM and Eterm. My
~/.xinitrc file was:
source /etc/bashrc
quartz-wm --only-proxy &
exec /usr/local/bin/e16
The problem started immediately after upgrading to OS-X 10.5.5. When
launching X11, the X11 icon would bounce forever in the dock, when I
ran top in a terminal window, I remember seeing multiple instances
of X11-related binaries starting up and dying constantly, including
xinit processes. I had never seen this before. The processes seemed
to spawn and die in waves, every few seconds, with each successive
wave more disk and cpu-intensive than the last. After about a minute
the machine had to be rebooted. This runaway effect happened across
several reboots, and would start each time I ran X11.app. Disabling
the launchd processes with Lingon actually prevented the respawning/
runaway condition, and allowed me to run startx by hand and look at
the errors.
I thought it was due to something stupid I did, so I ran thorough a
bunch of things to clean-up my system. I did not try to start X11
after each incremental change so I don;t know which thing fixed it.
There were some stray .XauthorityXXX files in my home directory that
I deleted, and some stray files and directories in /private/tmp/
from previous X11 sessions that I deleted. I also deleted ~/Library/
Preferences/org.x.X11.plist. I continued to get errors:
9/24/08 11:21:29 PM [0x0-0x3a03a].org.x.X11[555] dyld: Symbol not
found: __cg_jpeg_resync_to_restart
9/24/08 11:21:29 PM [0x0-0x3a03a].org.x.X11[555] Referenced from: /
System/Library/Frameworks/ApplicationServices.framework/Versions/A/
Frameworks/ImageIO.framework/Versions/A/ImageIO
9/24/08 11:21:29 PM [0x0-0x3a03a].org.x.X11[555] Expected in: /usr/
local/lib/libJPEG.dylib
EEK!
1) This would be not good indeed.
I have seen this error before and know it well, it is a conflict
between /usr/local/lib/libJPEG.xx and Apple's native JPEG library. I
used to get this error under Fink. The solution was tied to my bash
environment variable DYLD_LIBRARY_PATH.
Yeah, that forces libs to be loaded from paths specified in
DYLD_LIBRARY_PATH rather than what's explicit in the dylib. Over the
past year, I've gone from loving DYLD_LIBRARY_PATH to hating it for
this very reason.
When I comment out DYLD_LIBRARY_PATH from my /etc/bashrc, the JPEG
error goes away and the WM starts up normally. It's odd that the
presence of that env variable had no effect on running the same WM
binary under X11 1.0.
I'm curious if /System/Library/Frameworks/
ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/
Versions/A/ImageIO changed and this reference is new in 10.5.5.
I felt the error was due overall to my non-standard /etc/bashrc, so
i didn't bother to report it, or to see if others had that problem.
I couldn't reproduce the runaway effect problem, even after I
restarted the system daemons with Lingon.
Is the use of launchd with X11 something new since X11 1.0? If so,
the runaway condition might be tied to the respawning that is normal
under launchd.
launchd has been used to start X11 since 10.5 was first released.
What's new about 10.5.5 (and by new, I mean new to the OSX release
since around February, I think, in the macosforge.org releases) is the
use of xinit.
This is really all I can remember from the runaway condition. I can
reproduce the JPEG error, but I don't know what caused the runaway
condition. Let me know if you want more information or if you want
me to document this somewhere.
Thanks, this is *VERY* much appreciated.
--Jeremy
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
| References: | |
| | >X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Dave Ray <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Jeremy Huddleston <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Dave Ray <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Jeremy Huddleston <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Dave Ray <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Jeremy Huddleston <email@hidden>) |
| | >Re: X11 2.3.1 on Macbook Pro, Enlightenment, request for feedback on issues (From: Dave Ray <email@hidden>) |