| Re: X11 macOSX woes [message #39581 is a reply to message #39575] |
Thu, 27 May 2004 13:40   |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
"Karl Schultz" <kschultz_no_spam@rsinc.com> wrote in message
news:10bcgrvjms5l38a@corp.supernews.com...
>
> "Ben Tupper" <btupper@bigelow.org> wrote in message
> news:2hkbu8Fd6o4jU1@uni-berlin.de...
>> Hello All,
>>
>> I have been bumping into a real pain in the neck. It is a recent
>> occurance, but I can't pinpoint a cause/effect sequence of events.
>>
>>
>> The trouble is that *sometimes*, when the *last* open X11 window is
>> closed, X11 crashes and IDL outputs...
>>
>> IDL> X connection to :0.0 broken (explicit kill or server shutdown).
>>
>> before IDL quits. Closing the window can be a manual close (click on
>> the button) or a programmatic one (WDELETE).
>>
>>
>> Has anyone bumped into this problem, too? How would I chase down where
>> the problem lies.
>>
>> Thanks,
>> Ben
>>
>>
>> { ppc darwin unix Mac OS X 6.0.3 Feb 26 2004 32 32}
>
> We've *recently* seen this sort of problem here at RSI as well, but it
> involves iconifying or de-iconifying windows. For example, if you create
an
> IDLgrWindow, iconify it, and then destroy it, the X server will sometimes
> hang or crash. It seems that if you iconify or de-iconify the window and
> then destroy it very soon after that, the problem occurs more frequently
>
> Your problem and the other discussions in the thread aren't exactly this
> same as this, but there was enough similarity to mention it.
>
> I'm planning on filing a problem report with Apple. An X client shouldn't
> be able to make the X server crash, no matter what the client does.
>
One thing I just thought of that might be worth doing is to try using
another window manager. A window manager is just another client, but I have
to believe that the default window manager is "wired into" the system quite
a bit more tightly. Another simpler wm like twm might be worth trying. I
haven't tried switching the window manager (yet), but I would think that
there are some pretty simple instructions on the net someplace.
Trying another wm is just a temporary experiment, to see if the default wm
is part of the problem. If the change helps, it could be a workaround until
the server is fixed, if there is a server problem. I'm thinking that the
default window manager is so tightly integrated with the desktop that some
complication is causing the problem. A simpler, less integrated wm may not
have these complications. Just a guess.
Karl
Karl
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
