With the rise of the blogosphere, a greater number of people are now free to post their thoughts to the world - and because of the nature of the medium, there are a fair number of people writing about their experiences with computer software. Most software is not perfect, so some proportion of those experiences will be negative. In the special case of free software, all end users have the freedom to study and modify the source code. (It is easy to forget, having used GNU/Linux for a few years, that the licences of most proprietary software do not even give you the right to run the software in a debugger.) This does not imply, however, that the end user is necessarily capable of debugging any problems they run into themselves (although they do have the freedom to pay someone else to do so). In general, users will rely on the original developers of the software to fix any problems - and a good way to get the developers' attention is to file a report in the project's bug tracking system when there is one. It is unlikely that the developers will learn about problems through any other means. ...

Following my awesome coding on Pidgin yesterday, my brother has switched to aMSN. I had let slip at some point that his laptop's webcam would probably work with aMSN. The drivers themselves are included with the Ubuntu kernels, so that has never been a problem; however, because of some abstraction problems with Pidgin, there is still no webcam support with the MSN protocol. It almost worked with aMSN out of the box, but I had to open a port in the firewall to let people connect to him. (This is probably going to stop working when he's not in Derby, then.) Next, aMSN appears to only have OSS sound support, so I had to modify the Ubuntu menu entries to use the PulseAudio 'padsp' wrapper. This lets you record and play sounds, but the aMSN developers have not implemented continuous voice streaming yet, I think. ...

At the request of my brother, looked at Pidgin's mail notification dialog this evening. The Ubuntu package takes ages to build, unfortunately. The reported bug was that the 'Open Mail' button didn't work - looking at it, it's possible to select the mail you want to open on some services now, but by default nothing is selected. There's some code to desensitize the button in that case, but the initial state isn't set. My preferred patch would be to use GTK_SELECTION_BROWSE and some code to ensure that an email is always selected... I hacked together something that works for MSN, at least. It's short enough that it might not have too many serious bugs. ...

Who needs eclipse?

The bank holiday formed a welcome break after a hard week at work writing and fixing a Linux kernel module. On Friday afternoon version 0.4.3.1-1 of f-spot was uploaded to Debian, and then yesterday a new version of postgresql-autodoc. We've found a release-critical bug in f-spot already, of course. Most of the rest of my time was spent hacking on Angel, a project which we haven't formally announced yet. :) It still needs some refactoring before a public release is possible - there are a few bugs left to fix. Still, I'm hoping that we'll get there fairly soon. ...

Last night, I was granted permission to edit/close bugs on GNOME's bugzilla. Because of the logarithmic way in which the points system works, I now have three more bugzilla points than I did this morning. :)

A while ago, I mused on how network latency affects my email usage - one other cause of slowness in my mail client has been GPG key verification. Occasionally, when Evolution wants to check a signature, gpg takes 30 seconds or more to run, and the text of the message is not displayed until the end. The reason gpg runs so slowly is that it sometimes checks its trust database to make sure it's up to date. However, it does not make sense to run this at the time you are trying to verify an email - it will just slow you down. Fortunately, this is very easy to fix - add 'no-auto-check-trustdb' to gnupg.conf, and set up a nightly cronjob to run 'gpg --batch --check-trustdb'. Ensure that you have 'anacron' installed if your system is not always on. ...

Just over a year ago, Greg Kroah-Hartman announced the Linux Driver Project - companies could get Linux drivers written for their hardware free of charge, if they provided specifications (possibly under NDA). There is now an April 2008 Status Report for the project - they are short of companies and hardware to write drivers for. This is probably because Linux hardware support is excellent in all but a few specific areas - there is some interesting discussion of the efforts being made to support wireless devices and graphics cards later on in the thread. (If you're looking to get involved with Linux kernel development, cleaning up greg's LDP git tree would be a good place to start.) ...

I spent my weekend in Cambridge at the Debian bug squashing party. It was good seeing people again. I even squashed a bug, but then spent Saturday forwarding non-RC bugs upstream, and kernel hacking today. :) Walked back to Cambridge station - about 40 minutes, along the river for part of the way, and it was a nice evening. Living where I do, I don't walk as much as I used to... perhaps I should do more at weekends. ...

June 30 - "That's the last day when large computer makers — the Dells, HPs and Lenovos of the world — will be allowed to preinstall Windows XP on new PCs." -- Computerworld story What caught my eye about this was the fact that OEM manufacturers actually won't be allowed to continue installing XP. This seems quite odd to someone used to distributions of GNU/Linux - sure, security support from the distribution might end, and you might well be hard-pushed to find someone to support your seven year-old software, but if your customers want the older, faster version of the operating system, you will always be allowed to sell it.