Comment 21 for bug 680560

We've been informed that this bug is now fixed; however with no information about how or what the actual problem was. I followed the links to the referenced debian bug reports and couldn't find anything posted there. Mind sharing how Bug Watch knows that the bug is fixed and what the fix was?

Thanks.