<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: X11 Full Screen Support broken in Leopard, other changes, using Tiger&#8217;s X11&#8230;</title>
	<atom:link href="http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/feed/" rel="self" type="application/rss+xml" />
	<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/</link>
	<description>IRAF and More - For Mac Using Astronomers and Astrophysicists</description>
	<lastBuildDate>Mon, 01 Feb 2010 18:20:44 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mmhere123456</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20204</link>
		<dc:creator>mmhere123456</dc:creator>
		<pubDate>Wed, 31 Oct 2007 22:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20204</guid>
		<description>&lt;p&gt;another reason not to use the Leopard X11 is that LBX (low bandwidth X) is apparently not supported.  This feature is a complete MUST for me, as my home &#039;broadband&#039; connection, while high bandwith, unfortunately carries pretty high latency between home and work.&lt;/p&gt;

&lt;p&gt;Without LBX enabled, apps running at work and being displayed on Leopard X11 at home can take 45-60 seconds (!) for the initial window to appear.&lt;/p&gt;

&lt;p&gt;Because the default X protocol [without using LBX] is extremely chatty and sends a large number of tiny packets in a very interactive manner, it can be very slow across high latency links.  LBX solves this problem.&lt;/p&gt;

&lt;p&gt;I could live w/o full screen support, but no LBX is hideously bad!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>another reason not to use the Leopard X11 is that LBX (low bandwidth X) is apparently not supported.  This feature is a complete MUST for me, as my home &#8216;broadband&#8217; connection, while high bandwith, unfortunately carries pretty high latency between home and work.</p>

<p>Without LBX enabled, apps running at work and being displayed on Leopard X11 at home can take 45-60 seconds (!) for the initial window to appear.</p>

<p>Because the default X protocol [without using LBX] is extremely chatty and sends a large number of tiny packets in a very interactive manner, it can be very slow across high latency links.  LBX solves this problem.</p>

<p>I could live w/o full screen support, but no LBX is hideously bad!</p>]]></content:encoded>
	</item>
	<item>
		<title>By: michaelgalloy.com &#187; Leopard</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20154</link>
		<dc:creator>michaelgalloy.com &#187; Leopard</dc:creator>
		<pubDate>Tue, 30 Oct 2007 21:21:56 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20154</guid>
		<description>&lt;p&gt;[...] It appears that using Tigers X11.app should fix it for now. Link.     &#160; [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] It appears that using Tigers X11.app should fix it for now. Link.     &nbsp; [...]</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20124</link>
		<dc:creator>Marcos</dc:creator>
		<pubDate>Tue, 30 Oct 2007 00:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20124</guid>
		<description>&lt;p&gt;Bah, I&#039;m getting the eternal bouncing second X11 thing too.  I don&#039;t know why.  THe only work around I&#039;ve found is to &quot;show package&quot; contents of X11.app and make an alias of the &quot;MacOS/X11&quot; file.  Double clicking on that launches the terminal and launches x11.app but ... at least there&#039;s only one in the dock.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Bah, I&#8217;m getting the eternal bouncing second X11 thing too.  I don&#8217;t know why.  THe only work around I&#8217;ve found is to &#8220;show package&#8221; contents of X11.app and make an alias of the &#8220;MacOS/X11&#8243; file.  Double clicking on that launches the terminal and launches x11.app but &#8230; at least there&#8217;s only one in the dock.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Michael</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20105</link>
		<dc:creator>Scott Michael</dc:creator>
		<pubDate>Mon, 29 Oct 2007 20:39:31 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20105</guid>
		<description>&lt;p&gt;On my first attempt I neglected to remove the Leopard X11.app from /Applications/Utilities. Needless to say the launcher got really confused. After this I removed everything I could find in /usr/ and /etc/ relating to X11. I then followed the steps and was able to get a working Tiger X11 but still have the two icons in my dock. One works the other says Application Not Responding when I right click. If I &quot;Show in Finder&quot; it shows me /Applications/Utilities/X11.app for either one. So either I&#039;m starting two instances of the same thing and they aren&#039;t happy with each other. Or two different things, one which works, the other doesn&#039;t.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>On my first attempt I neglected to remove the Leopard X11.app from /Applications/Utilities. Needless to say the launcher got really confused. After this I removed everything I could find in /usr/ and /etc/ relating to X11. I then followed the steps and was able to get a working Tiger X11 but still have the two icons in my dock. One works the other says Application Not Responding when I right click. If I &#8220;Show in Finder&#8221; it shows me /Applications/Utilities/X11.app for either one. So either I&#8217;m starting two instances of the same thing and they aren&#8217;t happy with each other. Or two different things, one which works, the other doesn&#8217;t.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Marcos</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20104</link>
		<dc:creator>Marcos</dc:creator>
		<pubDate>Mon, 29 Oct 2007 20:25:21 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20104</guid>
		<description>&lt;p&gt;hmm.  I&#039;d think if you had uninstalled the leopard x11 you&#039;d be ok.  Is there still an X11.app file in /usr/X11 or wherever?    You could also check the x11-users archive; there&#039;s a lot of discussion there.  Can you &quot;reveal in finder&quot; the endless bouncing icon?  see what&#039;s going on as in where it&#039;s from.&lt;/p&gt;

&lt;p&gt;THere may be some plist still causing problems with launchd.&lt;/p&gt;

&lt;p&gt;When I get home I&#039;m going to try all this on my Macbook and I can report if I got it working.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>hmm.  I&#8217;d think if you had uninstalled the leopard x11 you&#8217;d be ok.  Is there still an X11.app file in /usr/X11 or wherever?    You could also check the x11-users archive; there&#8217;s a lot of discussion there.  Can you &#8220;reveal in finder&#8221; the endless bouncing icon?  see what&#8217;s going on as in where it&#8217;s from.</p>

<p>THere may be some plist still causing problems with launchd.</p>

<p>When I get home I&#8217;m going to try all this on my Macbook and I can report if I got it working.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Michael</title>
		<link>http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/comment-page-1/#comment-20103</link>
		<dc:creator>Scott Michael</dc:creator>
		<pubDate>Mon, 29 Oct 2007 20:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://macsingularity.org/2007/10/29/x11-full-screen-support-broken-in-leopard-other-changes-using-tigers-x11/#comment-20103</guid>
		<description>&lt;p&gt;This is a great tip! I&#039;d much rather use X11 from Tiger than try to fix the (broken) X11 included in Leopard. However, if I follow the instructions above, when I open the X11.app in /Applications/Utilities I get two icons in the dock. One which is the X11 I want and starts an xterm right away, the other just keeps bouncing and bouncing. Any  idea how to get rid of this second one? I&#039;m not sure if I didn&#039;t completely remove it or what exactly happened, also I&#039;m not sure how to find out what it&#039;s trying to execute.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>This is a great tip! I&#8217;d much rather use X11 from Tiger than try to fix the (broken) X11 included in Leopard. However, if I follow the instructions above, when I open the X11.app in /Applications/Utilities I get two icons in the dock. One which is the X11 I want and starts an xterm right away, the other just keeps bouncing and bouncing. Any  idea how to get rid of this second one? I&#8217;m not sure if I didn&#8217;t completely remove it or what exactly happened, also I&#8217;m not sure how to find out what it&#8217;s trying to execute.</p>]]></content:encoded>
	</item>
</channel>
</rss>
