Comment 11 for bug 563893

Revision history for this message
Mossroy (mossroy) wrote :

Had to use the workaround too (even after updating to 3.0.4+nobinonly-0ubuntu3) , but now it's fine