Ubuntu Wiki

From http://gould.cx/ted/blog/Saving_the_world_one__w_at_a_time

Please, for gnome-related packages use this upstream page: http://live.gnome.org/GnomeGoals/UseTimeoutAddSeconds

Saving the world one uW at a time

I'm here at UDS and joined a session between the kernel and desktop teams talking about power. Like all of such sessions the kernel team thinks that the desktop should fix all the problems and vice versa. At their suggestion, I took an action item.

One of the features of GTK+ is that it provides two timeout functions: gtk_timeout_add and gtk_timeout_add_seconds [1]. The difference is much more important than not having to add a "* 1000" in one and not the other. The important thing that the second function does is that it tried to group wake-ups to ensure that the program wakes up as little as possible. This is never perfect, but it's a small thing that can help to save some power and reduce the number of wake-ups.

So I looked through the Ubuntu main archive to figure out how many applications use the more precise function, but just pass in several seconds as the parameter. I figured this would be a few apps, and I'd submit a couple patches, then I could go back to blaming the kernel team for all our problems. There are more than a couple packages. There are a lot of packages. The results of the grep and a cleaned up list of packages that are likely to have easy fixes.

I realize now that I can't do this by myself, the only hope is to document how to fix it.

So if you'd like to help save a little power on your machine, follow these instructions.

Please, for gnome-relateed packages use this upstream page: http://live.gnome.org/GnomeGoals/UseTimeoutAddSeconds

1. Take one of the packages in the list above and find it in the package repository (instructions).

2. Branch it:

   • $ bzr branch http://package-import.ubuntu.com/x/xproject/jaunty localfix

3. Find the instances that might be causing the problem.

   • $ rgrep timeout_add *

4. Commit and build a package:

   • $ bzr commit -m "Saving the world"
     $ dch -i
     # aptitude build-dep xproject
     $ debuild

5. Test it on your system, make sure things still work reasonably.
6. Generate a patch:

   • $ bzr diff -r ancestor:

7. Submit it upstream!

[1] Note that PyGObject has timeout_add_seconds() but it was not documented.

Add your name to the Assignee column if you wish to tackle that package. After you have submitted the patch upstream, change row's background to yellow by adding <rowbgcolor="#ff9"> in the first cell of the column. After the patch has been commited upstream, change row's background to green by adding <rowbgcolor="#9f9"> in the first cell of the column. This will let people know that the package in that row has been hugged.