I'm glad I'm not the only one having this problem. I also get an
occasional complete crash like Steve reports:
> instead of freezing x11 just plain disappears. In either case
but usuallly I get the freeze with the quartz-wm error. Steve, do you
get this error if you look in
Applications/Utilities/Console after X11 dies?
quartz-wm[352] *** -[NSCFString toplevel_id]: selector not recognized
quartz-wm: caught exception: NSInvalidArgumentException - ***
-[NSCFString toplevel_id]: selector not recognized
On Tue, 12 Oct 2004 12:07:31 +0200, chris j. mutter <email@hidden> wrote:
> it could be also possible that you run into some kind of resource
> problem - i.e. a X11 server needs a lot of RAM when you run it in
> xinerama mode and/or high resolution/color depth - i had some X11
> crashes on older f/BSD boxes when they ran out of physical RAM.
> (i.e. use '% top -s vsize')
I don't think my problem is with resources, since I have 4 GB of RAM,
but I'll look at that. I might have some strange X resources set in
my .Xdefaults that quartz-wm is unhappy with. I've tried running X
with twm instead, and I haven't had the problem. But (IMHO) twm bites
so much that I haven't had the patience to use it for long.
Thanks,
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/x11-users/email@hidden
This email sent to email@hidden
