<?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: GNOME Power Manager unstableness</title>
	<atom:link href="http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/</link>
	<description>Blog about geeky stuff</description>
	<lastBuildDate>Sun, 22 Nov 2009 00:10:33 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Trial Lawyers</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1207</link>
		<dc:creator>Trial Lawyers</dc:creator>
		<pubDate>Wed, 03 Jun 2009 16:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1207</guid>
		<description>Glad I stumbled into this article! Finally, got what I was looking for to put on my school report</description>
		<content:encoded><![CDATA[<p>Glad I stumbled into this article! Finally, got what I was looking for to put on my school report</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1193</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Mon, 01 Jun 2009 20:37:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1193</guid>
		<description>Adam, even with the 2.26.2 build from koji?</description>
		<content:encoded><![CDATA[<p>Adam, even with the 2.26.2 build from koji?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1192</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Mon, 01 Jun 2009 20:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1192</guid>
		<description>Richard - I take it you&#039;ve seen the several responses on the fedora-test-list thread and in the bug report saying the git build I did hasn&#039;t fixed the problem for them?</description>
		<content:encoded><![CDATA[<p>Richard &#8211; I take it you&#8217;ve seen the several responses on the fedora-test-list thread and in the bug report saying the git build I did hasn&#8217;t fixed the problem for them?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1191</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Mon, 01 Jun 2009 10:25:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1191</guid>
		<description>@Michael: We did merge DeviceKit-power support in 2-25. And a lot of those changes happened only in 2-27, not stable branches,</description>
		<content:encoded><![CDATA[<p>@<a href="http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/#comment-1180">Michael</a>: We did merge DeviceKit-power support in 2-25. And a lot of those changes happened only in 2-27, not stable branches,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hughsie</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1190</link>
		<dc:creator>hughsie</dc:creator>
		<pubDate>Mon, 01 Jun 2009 09:38:52 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1190</guid>
		<description>@James, thanks for that -- the bug is in the xserver and we currently work around it in gnome-power-manager by setting a very small idletime alarm after a dpms state change. Hopefully it can be fixed in the X server without too many problems.</description>
		<content:encoded><![CDATA[<p>@James, thanks for that &#8212; the bug is in the xserver and we currently work around it in gnome-power-manager by setting a very small idletime alarm after a dpms state change. Hopefully it can be fixed in the X server without too many problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1189</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sun, 31 May 2009 18:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1189</guid>
		<description>I don&#039;t know if it&#039;s useful information to you since you&#039;ve probably figured this out by now, but if you look at the source for the xprintidle command, you&#039;ll find their workaround for the DPMS bug. I&#039;ve also written a python extension to get the correct idle time using that code if you&#039;re interested.

_J</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know if it&#8217;s useful information to you since you&#8217;ve probably figured this out by now, but if you look at the source for the xprintidle command, you&#8217;ll find their workaround for the DPMS bug. I&#8217;ve also written a python extension to get the correct idle time using that code if you&#8217;re interested.</p>
<p>_J</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Patryk "patrys" Zawadzki</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1188</link>
		<dc:creator>Patryk "patrys" Zawadzki</dc:creator>
		<pubDate>Sat, 30 May 2009 10:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1188</guid>
		<description>Adam:

I&#039;ve got it to work just after posting the first comment. I&#039;ve tried to post the the links two commits to devkit-power that are enough to make g-p-m fully build and work but it seems the spam filter ate them.

Richard:

I can confirm git master fixed the blackouts for me. Feel free to mail me if you need any harware info.</description>
		<content:encoded><![CDATA[<p>Adam:</p>
<p>I&#8217;ve got it to work just after posting the first comment. I&#8217;ve tried to post the the links two commits to devkit-power that are enough to make g-p-m fully build and work but it seems the spam filter ate them.</p>
<p>Richard:</p>
<p>I can confirm git master fixed the blackouts for me. Feel free to mail me if you need any harware info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blog Comments &#124; SEO Blog</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1187</link>
		<dc:creator>Blog Comments &#124; SEO Blog</dc:creator>
		<pubDate>Fri, 29 May 2009 23:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1187</guid>
		<description>[...] GNOME Power Manager unstableness « Technical Blog of Richard Hughes [...]</description>
		<content:encoded><![CDATA[<p>[...] GNOME Power Manager unstableness « Technical Blog of Richard Hughes [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1186</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Fri, 29 May 2009 19:51:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1186</guid>
		<description>for anyone on Fedora 11 (or, probably, 12...), here&#039;s some packages:

http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.i586.rpm

http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64.rpm

http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.src.rpm (just the source in case anyone wants it)</description>
		<content:encoded><![CDATA[<p>for anyone on Fedora 11 (or, probably, 12&#8230;), here&#8217;s some packages:</p>
<p><a href="http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.i586.rpm" rel="nofollow">http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.i586.rpm</a></p>
<p><a href="http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64.rpm" rel="nofollow">http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.x86_64.rpm</a></p>
<p><a href="http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.src.rpm" rel="nofollow">http://adamwill.fedorapeople.org/gnome-power-manager/gnome-power-manager-2.27.1-0.4.20090529git.fc11.src.rpm</a> (just the source in case anyone wants it)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Williamson</title>
		<link>http://blogs.gnome.org/hughsie/2009/05/29/gnome-power-manager-unstableness/comment-page-1/#comment-1185</link>
		<dc:creator>Adam Williamson</dc:creator>
		<pubDate>Fri, 29 May 2009 19:01:48 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/hughsie/?p=344#comment-1185</guid>
		<description>I have the same issue as Patryk.

Patryk, the offending commit is this one:

http://git.gnome.org/cgit/gnome-power-manager/commit/?id=90000eb88dbc4ef404f6be0940a0b64572c588ff

for a quick hack, grab that diff and apply it as a reverse patch to your build. (there&#039;s probably a &#039;proper&#039; way to do this with git&#039;s awesomeness, I dunno what it is though ;&gt;)</description>
		<content:encoded><![CDATA[<p>I have the same issue as Patryk.</p>
<p>Patryk, the offending commit is this one:</p>
<p><a href="http://git.gnome.org/cgit/gnome-power-manager/commit/?id=90000eb88dbc4ef404f6be0940a0b64572c588ff" rel="nofollow">http://git.gnome.org/cgit/gnome-power-manager/commit/?id=90000eb88dbc4ef404f6be0940a0b64572c588ff</a></p>
<p>for a quick hack, grab that diff and apply it as a reverse patch to your build. (there&#8217;s probably a &#8216;proper&#8217; way to do this with git&#8217;s awesomeness, I dunno what it is though ;&gt;)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
