<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Squib of the day: quit timeout</title>
	<atom:link href="http://blogs.gnome.org/metacity/2009/03/28/squib-of-the-day-quit-timeout/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/metacity/2009/03/28/squib-of-the-day-quit-timeout/</link>
	<description>"Many window managers are like Marshmallow Froot Loops; Metacity is like Cheerios."</description>
	<lastBuildDate>Sun, 08 Nov 2009 05:22:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Robin</title>
		<link>http://blogs.gnome.org/metacity/2009/03/28/squib-of-the-day-quit-timeout/comment-page-1/#comment-950</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Sat, 28 Mar 2009 11:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=554#comment-950</guid>
		<description>I see it a bit with big programs if the computer is busy: firefox, eclipse and open office mostly. But, it does let you wait. I don&#039;t think it&#039;s too bad as it is. 2.25 is something of an odd number though :)

What is more annoying, although probably not reasonably able to be controlled by the WM, is when you click &#039;close&#039; and the program doesn&#039;t because it&#039;s stuck in a way that leaves the GUI loop active, so you don&#039;t get the option of closing it without a command line kill or xkill. I guess what is happening there is that it&#039;s acknowledging the close but not actually closing because it&#039;s waiting on the stuck thread to finish. Fortunately this is fairly rare.</description>
		<content:encoded><![CDATA[<p>I see it a bit with big programs if the computer is busy: firefox, eclipse and open office mostly. But, it does let you wait. I don&#8217;t think it&#8217;s too bad as it is. 2.25 is something of an odd number though :)</p>
<p>What is more annoying, although probably not reasonably able to be controlled by the WM, is when you click &#8216;close&#8217; and the program doesn&#8217;t because it&#8217;s stuck in a way that leaves the GUI loop active, so you don&#8217;t get the option of closing it without a command line kill or xkill. I guess what is happening there is that it&#8217;s acknowledging the close but not actually closing because it&#8217;s waiting on the stuck thread to finish. Fortunately this is fairly rare.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: engla</title>
		<link>http://blogs.gnome.org/metacity/2009/03/28/squib-of-the-day-quit-timeout/comment-page-1/#comment-949</link>
		<dc:creator>engla</dc:creator>
		<pubDate>Sat, 28 Mar 2009 11:34:19 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=554#comment-949</guid>
		<description>well even nautilus triggers this often on my computer, a very slow old one. And Epiphany as well, but it deserves to be force quit anyway since it can&#039;t quit itself properly.</description>
		<content:encoded><![CDATA[<p>well even nautilus triggers this often on my computer, a very slow old one. And Epiphany as well, but it deserves to be force quit anyway since it can&#8217;t quit itself properly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon</title>
		<link>http://blogs.gnome.org/metacity/2009/03/28/squib-of-the-day-quit-timeout/comment-page-1/#comment-948</link>
		<dc:creator>Simon</dc:creator>
		<pubDate>Sat, 28 Mar 2009 09:49:33 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/metacity/?p=554#comment-948</guid>
		<description>The only program I recall seeing this message from is Firefox, where it happens quite frequently. No idea why, but closing FF always seems to take a few seconds, so it&#039;s often over that 2.25 second threshold.</description>
		<content:encoded><![CDATA[<p>The only program I recall seeing this message from is Firefox, where it happens quite frequently. No idea why, but closing FF always seems to take a few seconds, so it&#8217;s often over that 2.25 second threshold.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
