Comment 4 for bug 228988

The reason way it was set to confirmed (the other bug) is because last night me and Alexander had a talk about your bug in IRC and he still was a little shakey on what you meant as was I but we think we got to the bottom of what you meant. Not everyone is from the same country as you are so sometimes explaining a bug more than once is needed. You say you dont have time for this or your exact words were "PLEASE READ IT CAREFULLY, it's the last time I write, I have lost enough time." Writing things more than once is needed at time as developers and bug triagers we have to write the same thing over and over again for people to grasp it sometimes. Please be patient with us as we are trying to understand your problem and fix it as needed, If we need more info please feel free to give it to us without the threat of "PLEASE READ IT CAREFULLY, it's the last time I write".

Now i still think you need to file this upstream or look for the bug upstream. I might get to it in next few weeks but i have over 1000 other bugs i have to do the same with. Next week if i remember i will talk to Alexander about what he wants to do with this as an upstream bug or our bug, as in who will be working on this us or upstream