registry team mailing list archive

[Bug Watch Updater <185311@xxxxxxxxxxxxxxxxxx>]

Launchpad has imported 5 comments from the remote bug at
http://bugs.freedesktop.org/show_bug.cgi?id=14211.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2008-01-23T03:27:40+00:00 Timo Aaltonen wrote:

Forwarded from https://launchpad.net/bugs/185311 :

"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) ((xcb_req) - (dpy->request)) >= 0)' failed.
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb6def767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb6def81e]
#2 /usr/lib/libX11.so.6 [0xb76ca5f8]
#3 /usr/lib/libX11.so.6(XUnmapWindow+0x25) [0xb76c0fb5]
#4 libs/libSDL-1.2.so.0 [0xb7e76f01]
#5 libs/libSDL-1.2.so.0 [0xb7e7840e]
#6 libs/libSDL-1.2.so.0(SDL_VideoQuit+0x52) [0xb7e6e99a]
#7 libs/libSDL-1.2.so.0(SDL_QuitSubSystem+0x8c) [0xb7e50298]
#8 libs/libSDL-1.2.so.0(SDL_Quit+0x20) [0xb7e502ec]
#9 ./silverback.bin [0x80a95d3]
silverback.bin: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((xcb_req) - (dpy->request)) >= 0)' failed.
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0xb6def767]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x2e) [0xb6def81e]
#2 /usr/lib/libX11.so.6 [0xb76ca5f8]
#3 /usr/lib/libX11.so.6(XUnmapWindow+0x25) [0xb76c0fb5]
#4 libs/libSDL-1.2.so.0 [0xb7e76f01]
#5 libs/libSDL-1.2.so.0 [0xb7e7840e]
#6 libs/libSDL-1.2.so.0(SDL_VideoQuit+0x52) [0xb7e6e99a]
#7 libs/libSDL-1.2.so.0(SDL_QuitSubSystem+0x8c) [0xb7e50298]
#8 libs/libSDL-1.2.so.0(SDL_Quit+0x20) [0xb7e502ec]
#9 ./silverback.bin [0x80a95d3]
silverback.bin: ../../src/xcb_lock.c:77: _XGetXCBBuffer: Assertion `((int) ((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, neverwinter nights, causes the same problem on Hardy.
Here's a link to that:
http://ubuntuforums.org/archive/index.php/t-666726.html
"

Reply at: https://bugs.launchpad.net/ubuntu-
mobile/+bug/185311/comments/0

------------------------------------------------------------------------
On 2008-03-15T22:13:24+00:00 Josh Triplett wrote:

Jamey and I just announced a set of changes to XCB and Xlib/XCB which,
among other things, should address all the outstanding synchronization
problems that we know of.  Could anyone experiencing this bug please
build XCB and Xlib with the patches found at
http://lists.freedesktop.org/archives/xcb/2008-March/003347.html and
retest?

Reply at: https://bugs.launchpad.net/ubuntu-
mobile/+bug/185311/comments/22

------------------------------------------------------------------------
On 2008-06-19T11:56:24+00:00 Bryce Harrington wrote:

Several of those patches fail to apply to the last released libxcb.  Are
they in a git tree we can pull from?

Reply at: https://bugs.launchpad.net/ubuntu-
mobile/+bug/185311/comments/79

------------------------------------------------------------------------
On 2009-03-18T23:44:57+00:00 Bryce Harrington wrote:

Ping?  Any new status on this?

Reply at: https://bugs.launchpad.net/ubuntu-
mobile/+bug/185311/comments/202

------------------------------------------------------------------------
On 2009-07-06T14:02:54+00:00 Jamey-minilop wrote:

The socket handoff patches have been shipping for a while now. This bug
shouldn't be relevant any more. Sorry for the lack of feedback in the
meantime, though.

Reply at: https://bugs.launchpad.net/ubuntu-
mobile/+bug/185311/comments/206


** Changed in: xorg-server
   Importance: Unknown => Medium

-- 
hardy, locking assertion failure, xorg/libsdl
https://bugs.launchpad.net/bugs/185311
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.