Bug#498642: libx11-6: Locking assertion failure

[Subhashis Roy <subhashis3@fastmail.fm>]

Hi Julien,

I stripped a few lines before the messages I had sent "Locking assertion
failure.  Backtrace:"

The lines are:
-----------------
(WW) intel(0): Failed to set up write-combining range 
(0xe0000000,0x10000000)
Could not init font path element /usr/share/fonts/X11/cyrillic, removing 
from list!
*FvwmTaskBar: cannot open console
----------------

A few lines stripped after the message "#13 xv [0x804cc91]" assertion 
failure were:
---------
X Error: BadWindow (invalid Window parameter)
  Major Opcode:  4
-------------

Hope this helps (note that I am still using 'fvwm95' as my Window
manager. Though this was removed in Etch, I modified the '.deb' file to
correct the paths according to Etch's spec. of not having
'/usr/X11R6/bin' area, and used Soft links to circumvent the problem. I
also slightly changed its name to 'fvwm95.0').

Subhashis

On Fri, 12 Sep 2008, Julien Cristau wrote:

> On Fri, Sep 12, 2008 at 00:04:19 +0530, Subhashis Roy wrote:
>
> > Package: libx11-6
> > Version: 2:1.1.4-2
> > Severity: important
> >
> > I get the following error on the Console while starting the X-window
> > system using `startx'.
> >
> > --------------------------
> > Locking assertion failure.  Backtrace:
> > #0 /usr/lib/libxcb-xlib.so.0 [0xb7cc8767]
> > #1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb7cc881e]
> > #2 /usr/lib/libX11.so.6 [0xb7e8fdc9]
> > #3 /usr/lib/libX11.so.6(XUngrabServer+0x25) [0xb7e85d25]
> > #4 xv [0x805c32c]
> > #5 /usr/lib/libX11.so.6(_XError+0xd9) [0xb7e887b9]
> > #6 /usr/lib/libX11.so.6 [0xb7e90778]
> > #7 /usr/lib/libX11.so.6(_XReply+0x152) [0xb7e90b22]
> > #8 /usr/lib/libX11.so.6(XSync+0x67) [0xb7e84137]
> > #9 xv [0x805f924]
> > #10 xv [0x8055206]
> > #11 xv [0x804ecf9]
> > #12 /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7ce1455]
> > #13 xv [0x804cc91]
> > ------------
> You stripped the part of the error message that says which assertion is
> failing...
>
> Cheers,
> Julien