Bug#498642: libx11-6: Locking assertion failure
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-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498642: libx11-6: Locking assertion failure
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] Quite often I also notice that the Window manager cannot kill itself during Exit from X-Window (it sorts of hang there and I need to kill X with Ctrl-Alt-Backspace) which I do not know can be from the assertion failure. However, assertion failure for this package did not happen with Etch and I am noticing it only after upgrading to Testing. Since the backtrace shows failure mostly with '/usr/lib/libX11.so.6', which is part of 'libx11-6', I am filling bug-report against 'libx11-6'. Note that the xserver driver is 'xserver-xorg-video-intel' and the chip is Q35. -- Subhashis -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (101, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26.3 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libx11-6 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libx11-data 2:1.1.4-2 X11 client-side library ii libxcb-xlib0 1.1-1.1X C Binding, Xlib/XCB interface li ii libxcb1 1.1-1.1X C Binding libx11-6 recommends no packages. libx11-6 suggests no packages. -- debconf information: libx11-6/migrate_xkb_dir: true -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (101, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26.3 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages libx11-6 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries ii libx11-data 2:1.1.4-2 X11 client-side library ii libxcb-xlib0 1.1-1.1X C Binding, Xlib/XCB interface li ii libxcb1 1.1-1.1X C Binding libx11-6 recommends no packages. libx11-6 suggests no packages. -- debconf information: libx11-6/migrate_xkb_dir: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498642: libx11-6: Locking assertion failure
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#498642: libx11-6: Locking assertion failure
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 (0xe000,0x1000) 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
