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: Wed, 24 Sep 2008 22:59:24 -0700
On Sep 24, 2008, at 20:17, Dave Ray wrote:
On Sep 24, 2008, at 6:54 PM, Jeremy Huddleston wrote:
I recommend the utility Lingon to disable X11 in launchd.
Eh... why are you disabling X11 in launchd?
Technically I'm using Lingon to disable system agent "org.x.startx"
and system daemon "org.x.privileged_startx".
Reasons:
1) X11.app seems to run just fine without them. (Apple stock X11
under 10.5.4 and 10.5.5 also ran fine without these.)
Uhm...
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).
In other words, why would you disable it "just because it seems to
work without it"?
2) I maintain a pared-down system to get the best possible
performance for digital audio. Apple's system has become so inflated
with things I don't need, that collectively slow the performance,
that I have taken an aggressive posture with disabling unneeded
services using Lingon. I'm fairly seasoned and usually have good
luck adjusting system scripts, but occasionally I have a surprise
and have to revert a change.
Well, they don't actually run until you start them. There's no
performance gain from disabling them.
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.
Well, I'd much rather deal with it than ignore it. Please provide
some info to help us solve this problem you are having, since nobody
on this list or xquartz-dev has reported it.
Thanks for your help.
--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>) |