On Fri, Sep 12, 2008 at 00:04:19 +0530, Subhashis Roy wrote: > 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] > ------------
It seems the problem is that 'xv' calls XUngrabServer from its X error handler and thus tries to get the xcb lock a second time. Do things work better when upgrading libx11-6 and libxcb1 to experimental? Cheers, Julien -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
