> It now works fine! I don't know why, but it now works fine!
Can this be closed, then? Or shall we mark it as a dupe to bug 144073
> It now works fine! I don't know why, but it now works fine!
Can this be closed, then? Or shall we mark it as a dupe to bug 144073