Comment 14 for bug 1021946

I checked in a third computer and the bug is also there.

First approximation of what distinguishes the three computers:

- the two that suffer the bug are 64-bit sytems compared to the one that doesn't (32-bit)

- only the 32-bit was a fresh install, the other two (64-bit) were upgraded to precise from oneiric (one of them); and from natty, to oneiric, to precise (the other one)

it would be good to test fresh 64-bit installs and upgraded 32-bit, to see what's going on...