There's no error from the applet. There's nothing worth taking a screen shot. It applet just simply doesn't change the frequency. If you need more information, how about asking "Could you post the output of the ______ file after trying to switch the frequency?" or some other question that helps get the bug diagnosed instead of blaming the reporter. It's insulting to keep saying the bug report is poor when I already explained why it is not.
The devs at launchpad seem to fling around "closing this bug report because it lacks the information" even when the "lacks information part" is false. This policy alienates reporters. Instead of blaming bug reporters by saying the bug report is poor, the close message should be, "We are closing the bug because we have too few people and too many open bugs." That's still a bad policy but at least it's truthful and doesn't run the risk of false accusing someone of poor submissions. A few points: 1) Bugs do not rot. If it's policy to close them early, it's a bad one. 2) Even a poorly reported bug can evolve into a good submission with time. 3) Users will provide missing information if you ask. 4) They will be offended if you call their submissions poor. 5) They will be really offended if the submission is not poor but people keep saying so like Chatty-Kathy dolls. 6) Bug reporters might end up quitting their submissions. -- cpu frequency scaling monitor does not change frequency in Ubuntu Jaunty (9.04) alpha 5 on Core 2 system https://bugs.launchpad.net/bugs/337780 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
