The "export LIBXCB_ALLOW_SLOPPY_LOCK=1" did nothing good (or bad) for me, but the "non-xcb" version of libx11 did fix all problems I have seen. Note that on Sept 9th I have sent Bryce and this list a minimal X11 test program (source & binary) to reproduce the problem. It should help to debug the problem and verify a solution.
Let me know if you haven't received the test program and I will send you a copy.
Regards
Tom
--- On Thu, 11/9/08, Colin Watson <email address hidden> wrote:
From: Colin Watson <email address hidden>
Subject: [Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
To: <email address hidden>
Received: Thursday, 11 September, 2008, 1:56 AM
Could those people reporting
problems over the last half-dozen comments
or so please confirm whether the workaround Bryce posted works? Many
people have not mentioned this at all.
export LIBXCB_ALLOW_SLOPPY_LOCK=1
(Note that of course this has to be run in a terminal before starting
the application in question in the same terminal.)
--
hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a direct subscriber
of the bug.
Status in Ubuntu Mobile Edition: Confirmed
Status in X.Org X server: Confirmed
Status in “libxcb” source package in Ubuntu: Triaged
Status in “openoffice.org” source package in Ubuntu: Invalid
Status in “pygtk” source package in Ubuntu: New
Status in libxcb in Ubuntu Gutsy: Invalid
Status in openoffice.org in Ubuntu Gutsy: Invalid
Status in pygtk in Ubuntu Gutsy: New
Status in libxcb in Ubuntu
Hardy: Won't Fix
Status in openoffice.org in Ubuntu Hardy: Invalid
Status in pygtk in Ubuntu Hardy: New
Status in libxcb in Ubuntu Intrepid: Triaged
Status in openoffice.org in Ubuntu Intrepid: Invalid
Status in pygtk in Ubuntu Intrepid: New
Status in “libxcb” source package in Debian: Fix Released
Status in “libxcb” source package in Mandriva: Confirmed
Bug description:
Binary package hint: xorg
If I run Savage (a 3D non-open source game for Linux, available for download on
the internet), I get loads of these messages:
Hi Colin,
The "export LIBXCB_ ALLOW_SLOPPY_ LOCK=1" did nothing good (or bad) for me, but the "non-xcb" version of libx11 did fix all problems I have seen. Note that on Sept 9th I have sent Bryce and this list a minimal X11 test program (source & binary) to reproduce the problem. It should help to debug the problem and verify a solution.
Let me know if you haven't received the test program and I will send you a copy.
Regards
Tom
--- On Thu, 11/9/08, Colin Watson <email address hidden> wrote:
From: Colin Watson <email address hidden>
Subject: [Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
To: <email address hidden>
Received: Thursday, 11 September, 2008, 1:56 AM
Could those people reporting
problems over the last half-dozen comments
or so please confirm whether the workaround Bryce posted works? Many
people have not mentioned this at all.
export LIBXCB_ ALLOW_SLOPPY_ LOCK=1
(Note that of course this has to be run in a terminal before starting
the application in question in the same terminal.)
-- /bugs.launchpad .net/bugs/ 185311
hardy, locking assertion failure, xorg/libsdl
https:/
You received this bug notification because you are a direct subscriber
of the bug.
Status in Ubuntu Mobile Edition: Confirmed
Status in X.Org X server: Confirmed
Status in “libxcb” source package in Ubuntu: Triaged
Status in “openoffice.org” source package in Ubuntu: Invalid
Status in “pygtk” source package in Ubuntu: New
Status in libxcb in Ubuntu Gutsy: Invalid
Status in openoffice.org in Ubuntu Gutsy: Invalid
Status in pygtk in Ubuntu Gutsy: New
Status in libxcb in Ubuntu
Hardy: Won't Fix
Status in openoffice.org in Ubuntu Hardy: Invalid
Status in pygtk in Ubuntu Hardy: New
Status in libxcb in Ubuntu Intrepid: Triaged
Status in openoffice.org in Ubuntu Intrepid: Invalid
Status in pygtk in Ubuntu Intrepid: New
Status in “libxcb” source package in Debian: Fix Released
Status in “libxcb” source package in Mandriva: Confirmed
Bug description:
Binary package hint: xorg
If I run Savage (a 3D non-open source game for Linux, available for download on
the internet), I get loads of these messages:
silverback.bin: ../../src/ xcb_lock. c:77: _XGetXCBBuffer: Assertion `((int) libxcb- xlib.so. 0 [0xb6def767] libxcb- xlib.so. 0(xcb_xlib_ lock+0x2e) [0xb6def81e] libX11. so.6 [0xb76ca5f8] libX11. so.6(XUnmapWind ow+0x25) [0xb76c0fb5] 1.2.so. 0 [0xb7e76f01] 1.2.so. 0 [0xb7e7840e] 1.2.so. 0(SDL_VideoQuit +0x52) [0xb7e6e99a] 1.2.so. 0(SDL_QuitSubSy stem+0x8c) [0xb7e50298] 1.2.so. 0(SDL_Quit+ 0x20) [0xb7e502ec] xcb_lock. c:77: _XGetXCBBuffer: Assertion `((int) libxcb- xlib.so. 0 [0xb6def767] libxcb- xlib.so. 0(xcb_xlib_ lock+0x2e) [0xb6def81e] libX11. so.6 [0xb76ca5f8] libX11. so.6(XUnmapWind ow+0x25) [0xb76c0fb5] 1.2.so. 0 [0xb7e76f01] 1.2.so. 0 [0xb7e7840e] 1.2.so. 0(SDL_VideoQuit +0x52) [0xb7e6e99a] 1.2.so. 0(SDL_QuitSubSy stem+0x8c) [0xb7e50298] 1.2.so. 0(SDL_Quit+ 0x20) [0xb7e502ec] xcb_lock. c:77: _XGetXCBBuffer: Assertion `((int)
((xcb_req) - (dpy->request)) >= 0)' failed.
Locking assertion failure. Backtrace:
#0 /usr/lib/
#1 /usr/lib/
#2 /usr/lib/
#3 /usr/lib/
#4
libs/libSDL-
#5 libs/libSDL-
#6 libs/libSDL-
#7 libs/libSDL-
#8 libs/libSDL-
#9 ./silverback.bin [0x80a95d3]
silverback.bin: ../../src/
((xcb_req) - (dpy->request)) >= 0)' failed.
Locking assertion failure. Backtrace:
#0 /usr/lib/
#1 /usr/lib/
#2 /usr/lib/
#3 /usr/lib/
#4 libs/libSDL-
#5 libs/libSDL-
#6 libs/libSDL-
#7 libs/libSDL-
#8 libs/libSDL-
#9 ./silverback.bin
[0x80a95d3]
silverback.bin: ../../src/
((xcb_req) - (dpy->request)) >= 0)' failed.
Locking assertion failure. Backtrace:
Segmentation fault (core dumped)
I searched the web for this error, and it seems like running another 3d game, ubuntuforums. org/archive/ index.php/ t-666726. html
neverwinter nights, causes the same problem on Hardy.
Here's a link to that:
http://
Win a MacBook Air or iPod touch with Yahoo!7. http:// au.docs. yahoo.com/ homepageset