It appears that the cause of the problem was actually filesystem corruption on the machine I was using. I was booting the laptop off a USB disk with Ubuntu installed on it, and further tests indicated the faulty USB disk was to blame, causing all sorts of nasty fsck error messages. This bug should be closed, assuming others aren't encountering the same problem.
It appears that the cause of the problem was actually filesystem corruption on the machine I was using. I was booting the laptop off a USB disk with Ubuntu installed on it, and further tests indicated the faulty USB disk was to blame, causing all sorts of nasty fsck error messages. This bug should be closed, assuming others aren't encountering the same problem.