<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Intrepid Blog &#187; gnome</title>
	<atom:link href="http://blog.affien.com/archives/tag/gnome/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.affien.com</link>
	<description>A few thoughts</description>
	<lastBuildDate>Mon, 01 Mar 2010 00:58:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>&#8220;waiting for x server to begin accepting connections&#8221;</title>
		<link>http://blog.affien.com/archives/2008/06/29/waiting-for-x-server-to-begin-accepting-connections/</link>
		<comments>http://blog.affien.com/archives/2008/06/29/waiting-for-x-server-to-begin-accepting-connections/#comments</comments>
		<pubDate>Sun, 29 Jun 2008 17:19:58 +0000</pubDate>
		<dc:creator>Bas Westerbaan</dc:creator>
				<category><![CDATA[General]]></category>
		<category><![CDATA[gentoo]]></category>
		<category><![CDATA[gnome]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[X]]></category>

		<guid isPermaLink="false">http://blog.w-nz.com/?p=317</guid>
		<description><![CDATA[Try DisallowTCP = false under [Security] in /etc/X11/Sessions/Gnome/custom.conf or similar for other window managers.  Obviously this isn&#8217;t a very desirable solution, emerge --emptytree gnome might do the trick too. 
(and obviously this might be just one of the many underlying causes for the very generic symptom of X not accepting connections)
]]></description>
			<content:encoded><![CDATA[<p>Try <code>DisallowTCP = false</code> under <code>[Security]</code> in <code>/etc/X11/Sessions/Gnome/custom.conf</code> or similar for other window managers.  Obviously this isn&#8217;t a very desirable solution, <code>emerge --emptytree gnome</code> might do the trick too. </p>
<p>(and obviously this might be just one of the many underlying causes for the very generic symptom of X not accepting connections)</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.affien.com/archives/2008/06/29/waiting-for-x-server-to-begin-accepting-connections/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
