Comment 3 for bug 587118

That's the weird part--no, this is a brand new, stock KUbuntu install. We see the failure on both thin clients as well as right on the console. No fancy font packages installed, nor alternative libraries or special builds. We also see it on multiple browsers. I have debugging symbols and the source pulled, so I'll see what I can find out from examining a failed process, since it sounds like this is only being reported sporadically from the field. Note that this *is* a quad core i7, so it might be a threading thing.