XCB is a single-threaded protocol, and when called from a multi-threaded client application, that client needs to take care that its calls are properly thread-safe. Otherwise, it can trip assertions in the XCB code.
Which would mean this is not really a *bug* in xcb (any more than a syntax error would be a bug in gcc), but that xcb is catching a bug in the client application. Indeed, the assertion error text from xcb spell out the threading issue (or other similar issues commonly hit in code calling xcb_io.c functionality.) However, lots of code is MT and xcb is just too fragile, and the error text makes it look like the crash was in X so these issues tend to get filed against X components rather than investigated as client bugs. But I don't have a good idea what should be done on the X side. We're aware of some upstream work investigating these locking problems: http://article.gmane.org/gmane.comp.freedesktop.xorg.devel/29102 ** Changed in: libx11 (Ubuntu) Importance: Medium => High ** Changed in: libx11 (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Status in Modular X11 Libraries: Confirmed Status in “libx11” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Bug description: Here is a backtrace from Ubuntu Precise. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic-pae 3.2.0-rc5 Uname: Linux 3.2.0-5-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Date: Sat Dec 17 14:16:03 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1324036665 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcCmdline: nautilus -n ProcCwd: / Signal: 6 SourcePackage: nautilus StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. UpgradeStatus: Upgraded to precise on 2011-12-16 (1 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
