Comment 21 for bug 236778

Hi Sebastien. I have edited the title to reflect my understanding of this bug. I *think* what happened is that the original problem appeared in hardy-proposed and this bug was filed. Regardless of this bug the -proposed was pushed to updates, and as such people are commenting about having the issue without -proposed (I can confirm I have this issue without -proposed). THEN a fix for this issue was put in -proposed, so now proposed is fixed, while it is broken in an updated Hardy (reversed from initially when the bug was filed). Does that make sense? Can anyone confirm?