I’m thinking of buying an ASUS EEE 900A for testing power saving stuff and generally having a Fedora machine to travel with on the bus rather than the N800. Any advice? Thanks.
Does your project use PackageKit?
Yesterday, somebody asked me on IRC if there was a list of projects using PackageKit. I said no. I’m now adding a section on the website with just this content.
So, please send an email to me or the mailing list if your project is using PackageKit BY DEFAULT. This doesn’t mean “can be installed on”, but means “is usable when freshly installed”. I think it makes sense to add projects like nautilus that hook into the session interface too.
So far we’ve got replies from Fedora, Foresight, Moblin and Kubuntu. If you’re interested, please follow the instructions here or email me off-list. Thanks.
New web host
I’m looking for ideas for a web host to replace namezero. I’ve been with namezero for years and years for my personal website mostly due to laziness, but now their service has got beyond a joke and I’m looking for a replacement.
Can anyone recommend a (possibly UK based) hosting provider? I need about 1GB/month, about 50Mb webspace. I need just apache for static HTML pages, no MySQL, PHP, or any CMS fancy-whatsits. I need to transfer a single .com domain, and setup a few mail redirects — no mailboxes needed.
I don’t mind paying a little extra for uptime or for a company that isn’t going to go bust anytime soon. Ideas welcome. Thanks.
Richard.
GNOME Power Manager unstableness
Recently there has been a period of where gnome-power-manager wasn’t quite as stable and bug free as I would like. The reasons basically boil down to:
- Rewriting the engine to support DeviceKit-power rather than HAL
- Switching to using xbacklight rather than HAL to change the backlight (but falling back to HAL if xbacklight is not available)
- Rewriting the idle interactions to not rely on gnome-screensaver, but instead using gnome-session and X idletime
- Supporting HAL buttons and X buttons, and trying to filter out the duplicates
- Working around the fact that switching the monitor off using DPMS resets the IDLETIME…. urgh.
- Switching to using DeviceKit-power to do the suspend and hibernate, instead of using HAL
So, for the last few months I’ve been essentially trying to do the software equivalent of underpinning a house. I’ve spent the last couple of days adding more self check code, and fixing up the bugs that the new tests have found. Specifically, if your machine randomly switched off your display when you’re working, or when switching sessions didn’t restore your brightness correctly then git master probably might work for you.
Could people that have had problems, please try git master and give me success/failure as comments to the blog comment please. If the idletime and dimming stuff is 100% fixed now, then I’ll backport the fixes to stable and do a new release. Thanks.
p.s. If you change the value of GPM_USE_COMPOSITE in src/gpm-engine.c to 1 and recompile, then multiple batteries might work correctly too. Untested (still waiting for my ultra-bay battery to be delivered), so no promises.
I’m getting married
On Thursday I’m getting married. Due to this, I’ll be offline (and pretty much uncontactable) from today, for nearly a week. I’m also honeymooning later in May too, so if you send me mail or report bugs there might be a fair delay to me responding. Wish me luck!
PackageKit on FreeBSD
I’ve just checked a few fixes into git to fix the compile of PackageKit on FreeBSD. I’ve been using 7.1-RELEASE-p4 for testing.

Obviously, there is no pkg backend (hint, hint) but the dummy backend seems to be working well. Now all somebody has to do is contribute a backend!
GNOME PackageKit updates
A few nice things have been happening lately. The first is the re-versioning of 0.4.4 to 2.27.1, so that we can stick to GNOME release versions and the promise of release freezes. This should make it a bit easier for distributors, and will make the transition to gnome.org a little bit easier.
We’ve also been doing some tinkering around the edges to make things work better, hopefully without getting in the way. This is shown quite nicely from the following UI from the new update viewer.

And, thanks to Daniel Nicoletti, PackageKit now understands media requests, so the backends can request the user do something with physical media. This is still using the non-blocking logic we’ve always been using, so if we’re using multiple disks then the content has to be copied off each one in turn before the transaction, rather then installing direct from the media. Trust me, it’s better this way.

We’ve also been removing some dead code (libsexy, libglade, etc), and tidying up the existing objects, so hopefully 2.27.2 can be released in a few weeks. Comments, as always, welcomed.
Converting to GtkBuilder
This evening I’ve been trying to convert my projects (gnome-packagekit and gnome-power-manager) away from libgade to the shinier GtkBuilder. One less library, right? So far so good, except for the fancy super sexy custom widgets.
Stuff like the graph widget in gnome-power-statistics was created using the glade_set_custom_handler function, which was then creating the widget using gpm_graph_widget_new() in that callback. I’m not sure how to do this with GtkBuilder and the new markup format. Google isn’t being very helpful. Help appreciated. Thanks!
The next update viewer
We’ve got a new experimental update viewer in GNOME PackageKit. It looks something like this:
It’s currently called gpk-update-viewer2, and isn’t the default yet. I’ve patched Fedora rawhide to use it by default so we can get some early feedback and testing.
UI feedback welcome. Some of those strings are mighty difficult to understand, for instance, my fiancĂ©e didn’t know what a production system was. I also don’t like how the URL’s look. Ideas please. Thanks.
Application Installing (II)
I’ve been hacking more on the app-install framework. It’s now an independent project, with a tarball here.
What do the tools do?
$ app-install-create: creates the initial database, only used in the post section of the app-install package
$ app-install-add: adds data to the system database, used in repo packages
$ app-install-remove: removes data from the system database, used in repo packages
$ app-install-generate: generates the data for a desktop file, used when generating data from the distro helper
Now, the latter file is designed to be called from a distro specific helper, so for yum we do something like this:
$ app-install-generate-yum.py –repo=rawhide –dist=./dist
This downloads all the rawhide packages that ship a desktop file, uncompress them, and extract the data from the desktop files. There’s a cache, so repeated runs of this don’t have to re-download all the data. This tool takes about 10 minutes to run when the download has completed.
This tools creates ./dist/rawhide-icons.tar.gz and ./dist/rawhide.sqldata which are designed to be shipped in a distro package file.
In a package file, for instance, fedora-app-install, the post action would be something like:
$ app-install-add –repo=fedora –source=/var/lib/app-install/rawhide.sqldata
and in the preun:
$ app-install-remove –repo=fedora
I’m inviting other distros to submit distro generate tools, and I’ll ship them in the tarball.
