© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi Rogan,
I understand your frustration with the bug process and am sorry that it seems arbitrary and possibly unfair to you. However I'd like to ask for your understanding too, in that the Ubuntu project has limited resources, and the process is in place to make sure those resources are used as efficiently as possible. Thus rather than trying to keep track of all the people still having display related problems that *sound* similar to this one in this report, which is cumbersome, it would really help if, once verified that this fix doesn't help your (and others') particular problem, you could file a separate report, this enables bug triagers to work more efficiently (keep in mind most triagers are volunteers), and developers to better target and try to solve bugs that are more focused.
This is also the reason why we ask that you, the users, file the bug reports, instead of having a developer or triager trying to spin off all the remaining bugs, which would require creating them, subscribing each affected person, and then asking them to provide information via the apport tool. If you'd be kind enough to create the report yourself running apport (something the triager will ask for anyway), you'd be helping streamline the process, and it would be a great help to the project as a whole.
From reading your description, your issues sound more driver or kernel-related than Unity-related (which is what this bug was about). Thus, it would really be more helpful if you would create a new report, which will contain hardware-specific information (that's one thing about *this* bug: it was NOT hardware-specific, I tested it on a lot of systems from different makes and models, that's why it was filed with such a broad list of machines, and eventually fixed exclusively in Unity).
When you do that, I suggest you mention, in your report's description, that you've followed progress on this bug (give the number) and the posted solution didn't work for you. Then the triager will be sure to *not* close it as a dupe of this one. I can assure you that triagers *do* read the bug reports and we won't just summarily dismiss it because it sounds somewhat similar to something else.
Thanks for your understanding and please let me know if you have other concerns.
---
Daniel Manrique
Ubuntu Bug Squad volunteer triager
http://