Bug#498642: marked as done (libx11-6: Locking assertion failure)
Your message dated Sat, 6 Mar 2010 15:49:16 +0100
with message-id <20100306144916.GA5643@loulous.org>
and subject line Re: Bug#498642: libx11-6: Locking assertion failure
has caused the Debian Bug report #498642,
regarding libx11-6: Locking assertion failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
498642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libx11-6: Locking assertion failure
- From: Subhashis Roy <subhashis3@fastmail.fm>
- Date: Fri, 12 Sep 2008 00:04:19 +0530
- Message-id: <20080911183419.24455.14165.reportbug@roy.ncra.tifr.res.in>
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.1 X C Binding, Xlib/XCB interface li
ii libxcb1 1.1-1.1 X 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.1 X C Binding, Xlib/XCB interface li
ii libxcb1 1.1-1.1 X C Binding
libx11-6 recommends no packages.
libx11-6 suggests no packages.
-- debconf information:
libx11-6/migrate_xkb_dir: true
--- End Message ---
--- Begin Message ---
- To: 498642-done@bugs.debian.org
- Subject: Re: Bug#498642: libx11-6: Locking assertion failure
- From: Brice Goglin <Brice.Goglin@ens-lyon.org>
- Date: Sat, 6 Mar 2010 15:49:16 +0100
- Message-id: <20100306144916.GA5643@loulous.org>
- In-reply-to: <20090131215937.GA5911@radis.liafa.jussieu.fr>
- References: <20080911183419.24455.14165.reportbug@roy.ncra.tifr.res.in> <20090131215937.GA5911@radis.liafa.jussieu.fr>
On Sat, Jan 31, 2009 at 10:59:47PM +0100, Julien Cristau wrote:
> 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?
No reply in a year, closing.
Brice
--- End Message ---
Reply to: