Comment 48 for bug 1163886

Stian Liknes (stianlik) wrote :

The workaround in comment #31 fixed the problem for me also.