| Summary: | vino-2.16.0 fails a lock assertion using XCB | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Mike Auty <mike.auty> |
| Component: | * Other | Assignee: | Josh Triplett <josh> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | high | CC: | dberkholz |
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| URL: | http://bugs.gentoo.org/show_bug.cgi?id=151397 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Mike Auty
2006-10-15 09:07:59 UTC
This bug doesn't belong to XCB; this assertion from XCB just means that something called UnlockDisplay when it didn't have the display locked. This assertion should always indicate a bug in some software invoking Xlib/XCB, rather than a bug in Xlib/XCB itself. A backtrace might help us track down who we should reassign this bug to. In the meantime, I've made this bug no longer block the 1.0 release-tracking bug 6797. I've managed to reproduce this problem here. Versions: vino from Debian package 2.13.5-3 libX11 from current GIT, commit 256eba6b40c5f811a03b04abf5f85f728ee3ab5d libXCB 1.0-RC2 Current unstable versions of Xorg libraries, which correspond roughly to Xorg 7.1: ii libxau6 1.0.1-2 X11 authorisation library ii libxaw-headers 1.0.2-4 X11 Athena Widget library (development heade ii libxaw7 1.0.2-4 X11 Athena Widget library ii libxcomposite1 0.3-2 X11 Composite extension library ii libxcursor1 1.1.7-4 X cursor management library ii libxdamage1 1.0.3-2 X11 damaged region extension library ii libxdmcp6 1.0.1-2 X11 Display Manager Control Protocol library ii libxevie1 1.0.1-3 X11 EvIE extension library ii libxext6 1.0.1-2 X11 miscellaneous extension library ii libxfixes3 4.0.1-4 X11 miscellaneous 'fixes' extension library ii libxfont1 1.2.2-1 X11 font rasterisation library ii libxft2 2.1.8.2-8 FreeType-based font drawing library for X ii libxi6 1.0.1-3 X11 Input extension library ii libxkbfile1 1.0.3-2 X11 keyboard file manipulation library ii libxkbui1 1.0.2-2 X11 keyboard UI presentation library ii libxklavier10 2.2-3 X Keyboard Extension high-level API ii libxmu-headers 1.0.2-2 X11 miscellaneous utility library headers ii libxmu6 1.0.2-2 X11 miscellaneous utility library ii libxmuu1 1.0.2-2 X11 miscellaneous micro-utility library ii libxp6 1.0.0.xsf1-1 X Printing Extension (Xprint) client library ii libxpm4 3.5.5-2 X11 pixmap library ii libxrandr2 1.1.0.2-4 X11 RandR extension library ii libxrender1 0.9.1-3 X Rendering Extension client library ii libxres1 1.0.1-2 X11 Resource extension library ii libxss1 1.1.0-1 X11 Screen Saver extension library ii libxt6 1.0.2-2 X11 toolkit intrinsics library ii libxtrap6 1.0.0-4 X11 event trapping extension library ii libxtst6 1.0.1-5 X11 Testing -- Resource extension library ii libxv1 1.0.2-1 X11 Video extension library ii libxvmc1 1.0.2-2 X11 Video extension library ii libxxf86dga1 1.0.1-2 X11 Direct Graphics Access extension library ii libxxf86misc1 1.0.1-2 X11 XFree86 miscellaneous extension library ii libxxf86vm1 1.0.1-2 X11 XFree86 video mode extension library Backtrace (just with debugging symbols from -dbg packages): #0 0xffffe410 in __kernel_vsyscall () #1 0xa774a821 in raise () from /lib/tls/i686/cmov/libc.so.6 #2 0xa774bfb9 in abort () from /lib/tls/i686/cmov/libc.so.6 #3 0xa7743fcf in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 #4 0xa7248770 in xcb_xlib_unlock (c=0x808aa60) at xcb_xlib.c:50 #5 0xa78f55d4 in _XCBUnlockDisplay (dpy=0x808a520) at xcb_lock.c:34 #6 0xa789ffdb in XDamageQueryVersion (dpy=0x808a520, major_versionp=0xaf9dca00, minor_versionp=0xaf9dc9fc) at ../../src/Xdamage.c:308 #7 0x0804ec71 in ?? () #8 0x0808a520 in ?? () #9 0xaf9dca00 in ?? () #10 0xaf9dc9fc in ?? () #11 0x080b0d20 in ?? () #12 0x00000000 in ?? () I've tracked this down to a bug in XDamageQueryVersion: it calls UnlockDisplay and SyncHandle without having called LockDisplay. I've fixed this in libXdamage master, in commit 31829be123a9ce58bf8e0c4718815b7b63d0d512. I've tracked this down to a bug in XDamageQueryVersion: it calls UnlockDisplay and SyncHandle without having called LockDisplay. I've fixed this in libXdamage master, in commit 31829be123a9ce58bf8e0c4718815b7b63d0d512. Wow, one hour turn around! Sorry to have filed it under the wrong component. Thanks again for fixing it so quickly, I can't wait to see hit XCB hit the mainstream... 5:) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.