Comment 17 for bug 152820

Hi Bolek, thanks for the update. I'm going to close this report for now as this is no loner an issue for you.

Kamba, I'll follow up with you at bug 151088. However, just to answer some of the questions you raised here. . . the reason we ask that bug reports specifically target one particular bug on a specific set of hardware is so that it is easier for our development teams to focus on a fix. If you report a bug that says for example "Sound is broken" or "Suspend/Resume fails", that's a very generic issue. Depending on the type of hardware you have, you'll be exercising different drivers, and probably be requiring different fixes. If we don't narrow the report down to a specific target, the report can grow wildly out of control and not be very useful to the team debugging the issue nor to any reporters who are subscribed to the bug. Also, as you can see with what happened in this report, the bug will be sometimes be resolved for some but not for others. This often leads to confusion and frustration not only for bug reporters but also for our development teams. It is unfortunate that some new bug reports do remain in the "New" and "Unassigned" state. It is not a matter of importance regarding the bug, but rather an issue of resources. We are actively trying to resolve this situation. We really do appreciate the reports users like yourself submit and apologize for any sort of frustration that may arise. I hope this helped explain things a little. Thanks.