Comment 13 for bug 429610

Revision history for this message
Diederik van Lierop (mail-diedenrezi) wrote :

This bug was caused by the patch attached to bug 168384. This patch has been reverted though, so everything should be working properly again.