[Xcb] Nested XLockDisplay

[Barton C Massey]

Bug found (by me) and fixed (by keithp).  Check out the
just-committed libXrandr to get the fixes.  Sorry it took us
so long.

I'll close out the XCB bug---we'll let you figure out how to
get the other one closed.

Thanks much once again for reporting this.  We'll try to be
more responsive in the future. :-)

	Bart

In message <c912665b0701060201j459719dch24f151d58e3e65b1 at mail.gmail.com> you wrote:
> Hi Barton,
> 
> I'm already using the latest development version of Xrandr fetched
> with git. I'm also using the git version of libXext since that seems
> to be in the backtrace of the assertion error. The error is still
> there. Is it possible one of you guys could try my small test case so
> see if I've done anything wrong?
> 
>  - elias
> 
> On 1/5/07, Barton C Massey <bart at cs.pdx.edu> wrote:
> > In message <c912665b0701050316w278604b0g2aeeefd640257f at mail.gmail.com> you wrote:
> > > On 1/4/07, Josh Triplett <josh at freedesktop.org> wrote:
> > > > Nested calls to XLockDisplay, in the public API, work fine.  Nested calls to
> > > > LockDisplay, in Xlibint.h, do not.  Things which trigger this assertion have
> > > > used an internal-only call which only extension libraries should use.  In
> > > > this case, as you mentioned in a later mail, libXrandr makes the problematic
> > > > call.
> > > >
> > > > - Josh Triplett
> > > >
> > >
> > > Hi Josh,
> > >
> > > Thank you for the explanation. I was confused by the "LockDisplay"
> > > name, which I assumed was XLockDisplay the same way OpenGL specs strip
> > > the "gl" prefix.
> > >
> > > With that out of the way, is there anything I can do to help fix this
> > > bug (apart from the test program and backtrace)?
> >
> > Start by making sure you have the very latest libXrandr: I
> > think we've fixed at least one locking bug there already.
> >
> >         Bart
> >
> >