Path: utzoo!attcan!uunet!husc6!mailrus!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: X11R3 server bug?
Message-ID: <8811030034.AA24245@EXPO.LCS.MIT.EDU>
Date: 3 Nov 88 00:34:51 GMT
References: <8480@cit-vax.Caltech.Edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19


    In running an application which redefines the color maps for all windows
    under the root window of the display I seem to have done *something* which
    breaks my X server.

As usual, it would help a lot to know a lot more about exactly what your
code is doing.  But, here is a wild guess.  If you are creating a new
colormap and storing as the colormap attribute of the root window, and
then having that client terminate with a CloseDownMode of DestroyAll,
then the result is that the colormap gets destroyed and the root window
ends up with a colormap of None.  All further attempts by clients to
create a top-level window with colormap CopyFromParent (which is what
most clients do) will get a BadMatch error because the colormap of
the parent is None.

The protocol probably ought to special-case the root window and
force its colormap back to the default colormap, but on the other
hand, you shouldn't be playing with global resources without
proper supervision. :-)