Comment 9 for bug 228063

This problem seems to have gone away with the recent official and full release of Firefox 3.

Not too sure if the solution was in Firefox 3 itself or the barrage of updates some of which were kernel updates etc.