<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Assertion `c-&gt;xlib.lock&#8217; failed</title>
	<atom:link href="http://blog.felisberto.net/2008/01/29/assertion-c-xliblock-failed/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.felisberto.net/2008/01/29/assertion-c-xliblock-failed/</link>
	<description>Life, the universe and all the rest</description>
	<pubDate>Wed, 15 Oct 2008 20:22:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: John Myers</title>
		<link>http://blog.felisberto.net/2008/01/29/assertion-c-xliblock-failed/#comment-49621</link>
		<dc:creator>John Myers</dc:creator>
		<pubDate>Wed, 30 Jan 2008 01:47:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.felisberto.net/2008/01/29/assertion-c-xliblock-failed/#comment-49621</guid>
		<description>with a recent xcb you can also just put LIBXCB_ALLOW_SLOPPY_LOCK=1 in your environment, which suppresses that assertion.</description>
		<content:encoded><![CDATA[<p>with a recent xcb you can also just put LIBXCB_ALLOW_SLOPPY_LOCK=1 in your environment, which suppresses that assertion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
