Comment 91 for bug 950160

Daniel van Vugt (vanvugt) wrote :

The recommended workaround is "WORKAROUND 1" listed at the top of the bug.