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: Dave Ray <email@hidden>
- Date: Thu, 25 Sep 2008 00:48:57 -0700
On Sep 24, 2008, at 10:59 PM, Jeremy Huddleston wrote:
org.x.privileged_startx insures that you have your font caches
updated and fixes permissions in /tmp to not make you possibly
vulnerable to attacks from local users.
org.x.startx is what makes X11 startup automatically when you run
stuff from Terminal.app (for example). Other applications actually
RELY on $DISPLAY being set when they start (Gimp, Inkscape,
OpenOffice, etc).
Thank you again Jeremy for enlightening me to some of these issues.
I'm very new here and have more experience under Linux X11.
I reset the system agent and daemon to be active at your suggestion.
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.
3) When I upgraded from 10.5.4 to 10.5.5 and launched X11.app, not
only did X11 not activate properly, it caused a runaway condition
where X-related processes were respawning, using more memory and
cpu, faster than I could kill processes at the prompt.
Well, why didn't you report this problem? There is an automated
submission of a condition like this in our bug database, but nobody
can reproduce it, and there are no useful comments. If you could
indicate what it was that was unique to your configuration over the
default, it would be a big help in getting this fixed.
My hard drive was churning and cpu was pegging at 100%. I could
only recover form the runaway condition with "sudo shutdown -r
now". I had to disable the X11 agents and daemons with Lingon in
order to be able to run startx at the terminal without the
respawning, then debug and fix what was going on. After X11 worked
again, I decided not to set them back. If a similar problem happens
in a future upgrade I don't want to deal with the respawning issue.
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
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. 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
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.
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.
-Dave
_______________________________________________
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>) |