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: Wed, 24 Sep 2008 20:17:16 -0700
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.)
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.
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. 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.
There's nothing wrong with the daemon/agent specifically, and this is
not a 2.3.1-specific issue, but is there any reason I should leave
those on?
Under Apple's X11, when I start X11, only what I have in
my .xinitrc file is launched. When I exit the window manager with
its own X11-based menus, X11.app also exits automatically. This
would be the desirable behavior for the development X11 release.
That is the behavior. We are using xinit, so this behavior is the
same on OSX as it is on Linux.
Hmmm.. I am not seeing that on my system. When I exit Enlightenment
WM, X11.app continues to run until I quit it manually.
hmm... waitasec... yeah, you're right... hmm... I think I just
figured this out... I don't have a solution for it and I'll have to
think about it a bit...
I ran top in a terminal window to see what X11-related processes
were running after quitting my WM, and only X11.app was running in
that state. Is this a bug?
Yeah, kinda... more like I didn't predict people trying to use X11
on OSX this way quite yet (I wanted some breathing time with a
working quartz-wm X11 before people tried things like other WM/SMs).
....
That's not going to be resolved for a while... Please file a bug
report and hopefully I can figure something out for 2.3.2 for ya.
Thanks again for the feedback, I will file two bugs - 1) menu bar
issue 2) app not quitting.
-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