Comment 63 for bug 575160

Revision history for this message
In , Andrew-williams (andrew-williams) wrote :

I have just updated the bug referred to in comment 11 - which is almost certainly the problem addressed in comment 12 - saying that the new package referenced in comment 14 appears to have solved bug 626042.
Two for the price of one?