Comment 73 for bug 375148

Ahmed, what's that nonsense now? AFAIK, according to your statements here, you never successfully reproduced this issue or did you? How can you be sure now this issue is fixed? In any case, don't you think you should at least give the people affected a chance to confirm that the problem is indeed gone?

FWIW, a very quick test showed that of course this is not fixed (please explain why you think it was). To make a long story short, *NOTHING* has changed since I originally reported this approaching two years now. I have nothing to add, no progress to report to any of my earlier statements, they are still true with the latest package.

Ahmed, I urge you to really shape up your bug work now. Don't just claim it works when you cannot know (and in fact it doesn't). Don't constantly churn out untested packages that don't even compile or install in the hope that somehow one of them magically fixes everything. I beg you, please!