Comment 3 for bug 516219
Revision history for this message
| lelamal (lelamal-deactivatedaccount) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
> Thank you for taking the time to report this bug.
You're welcome.
> However, it is a duplicate of bug #515495.
And how would I know? If it was up to me to decide, I would have followed Apport, and considered bug #515495 itself to be a duplicate of Bug #422393. However, I have been told that was not the case for the latter was fixed, so I followed his advice.
> Even though Sebastien requested you to report
> a new bug instead of reopening the old bug, you don't have to create
> three. One is enough.
One may be enough now, but not before. Again: how would I know when could that have been enough? I had been instructed to use Apport to open a new bug for it might have been a different or new issue... but then I thought that Apport is the same tool whose precision I had been instructed to question and ignore, so I believed it safer to report each new instance of this particular bug and wait for retraicing. In the end, I am an average user, while Sebastien is the expert, and I would never question his word. Anyway, now that I have an official word on the matter, I know it is useless to keep reporting this bug.