Comment 2 for bug 156536

I still see it sometimes, but more rarely. It's become one of those things that's fluttering at the edge of traceability. That machine actually has two versions of Ubuntu on it right now. My feeling is that the problem is less common with Hardy Heron, but more common with Gutsy. When it does happen, the condition seems to persist, though sometimes resetting the project will start it on a work unit that does not hang. (Other times multiple resets have no effectiveness.)

I basically feel like this is outside of Ubuntu's scope, but is a work unit allocation problem on the project end. You'd think that the size of the problems would be matched to the resources of the volunteer's machine, but if that's supposed to happen, then sometimes it fails.

Since no one else has commented on the bug, I suppose we can assume it's quite rare, though the machine that shows it is a very vanilla IBM NetVista. On the old side, but certainly not a rare machine in its day. This one actually has some extra memory above the original factory installed.