Here is a real life story. I noticed that Evolution crashed when I tried to reply to a mailing list message. Keen to do my bit, I searched Malone for "mailing list", which found nothing similar to my bug. When Evolution crashed the next day (Why does apport only notify about an application crashing the first time in a session), I submitted a bug report via apport. This involved uploading rather a large number of megabytes of data to Malone, this took quite long on a 256Kb upload line. Once Epiphany appeared, I changed the name of the bug report to something more descriptive ([apport] Evolution crashes after trying to reply to mailing list). Thanks to this, the duplicate search didn't find the often-duplicated bug #85159. I proceeded with the report, which became bug #99415, which became a duplicate of #85159 soon afterwords. This prompted me to file this request, and to apologise for filing another duplicate of #85159 (one of 28).
2 lessons should be learnt from this story: 1. It is unreasonable to ask that users should upload vast amounts of data to Malone without any assurance that the resulting bug is a duplicate. 2. Somebody might modify their bug's name, causing the duplicate suggestion to not work. -- Duplicate searching needed https://bugs.launchpad.net/bugs/103083 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
