Thanks for your response. On 2010-10-31 12:26, papukaija wrote : > According to LP, this bug is affecting 1 person (as seen on the top of > this bug report). That's one reason for this bug for not being marked as > confirmed. Please understand the meaning of the word shudder. You seem not to have noticed that even those who comment bugs do not use the counter. Visit the 10 bug numbers next ton this one and you will find 10 bugs not affecting anyone and yet confirmed or even better. Why did Alexander Sack, and at least 3 persons meet the bug and not count it? You seem not to understand what ThiloPfennig wrote : > To start with the first example mentioned in the bug report if I > access the page: http://atilf.atilf.fr/tlf.htm Firefox sets encoding > to UTF-8. Neither this > I have another example where things do not work well: > http://www.kodak.com/eknec/PageQuerier.jhtml?pq-path=12368&pq-locale=de_DE&CID=KOSBANNER&LOC=290808_CRM_F1_M863 > As well as the next comment showing that Firefox had used !!!! ASCII !!! for that page. Why were those persons not asked to provide more URLs for the collection? This bug reporting business is complete nonsense. Bug #206884 reports exactly the same problem as this one. Someone changed the title, confirmed it and linked it to something totally different. And, for the LP addicts, you can take one more count from there for this one. We're nearing 10 there and you count 1. > Secondly, you were asked (first time in comment 28) to > provide an other URL to test this bug. In comment 53 you gave one but > that's not working and concerning operaliege.be, I am not going to give > my bank details to them. I am not laying URLs. Please try to understand that the best way to have a payment fail is not giving any bank detail. I'm sorry I can't choose the circumstances in which I meet this bug. Could you please understand that after trying all the examples I and other persons showed, it's no use to keep asking more URLs if there's a reason why that bug will never show on your computer as obstinately as it shows on all mine and that the matter is to understand why. > Btw, > are you referring to Maverick by "fresh Ubuntu" ? In VirtualBox, I have Ubuntu 10.04, 10.10, Windows 1.01, XP and 7 all exhibiting the Bug with native Firefox or its latest Ubuntu update. Maverick has 3.6.10 and my running Lucid 3.6.11. > Finally, you (or anyone else affected by this > bug; but that's not the case according to LP) Could you please let that LP alone? > you were asked in comment 51 > to report this bug upstream. Reporting this bug upstream would give this > bug "Triaged" as status and that status has higher importance than > Confirmed, so you're strongly recommended to report this bug upstream. I > can't report this bug upstream since I can't reproduce this bug. And you were asked not to remove confirmed status. What I was actually asked is this: "Please help us improve Ubuntu by reporting bugs" what I did 2½y ago, and later without warning : "Thank you for spending your time [and they don't imagine how much] helping to make Ubuntu better with this bug report. Reporting a bug is the first step in the bug fixing process. As a part of that process you may need to answer some questions to help developers work on your bug." I welcome developers in addition because each time I met someone who understood the problem, the matter was solved in a few days of dialog. But I've never seen a developer the Ubuntu way, even after 1, 2 or 3 years. I wasn't asked and I'm not supposed to know all Ubuntu's suppliers, nor to have any competence to discuss software administrativia with them and I have no time for that. Ubuntu should really automate two-way peering of bugs DBs and the best idea would be to start an independent central DB with a common protocol definition to act as a hub between the other sites. That would really help Ubuntu more that the pages you made me write. Thanks in advance. I like to report bugs to Launchpad because it's normally the way users find practical solutions to their problems. But Launchpad isn't normal. For bugs that don't stay 3 years without attention but get a correction, there is usually no such practical solution, just sharing the joy or Ubuntu that the bug will be fixed in the next release. Les lendemains qui chantent. However, in hope that the time you all made me loose is not completely lost, I have opened this. https://bugzilla.mozilla.org/show_bug.cgi?id=608609