Comment 58 for bug 361689

It happened after a reboot - I blamed this update due to the "hal" in the error message.

I've downgraded ("sudo apt-get install hal/jaunty libhal1/jaunty libhal-storage1/jaunty") but the problem remained through several reboots until I did a shutdown and then poweron.

Therefore I suspect some part(s) of the hardware might have been in a weird state and there is nothing wrong with the update.