Comment 2 for bug 823588

Hi Jeff, sorry to hear you had such troubles. Unfortunately this bug report as written is non-actionable. Here's a few tips for improving your bug report:

1. Attach log files. Without log files developers cannot diagnose the problem. Generally, running 'apport-collect 823588' should attach the required files.

2. When writing a bug report description, try to think of it more like a high school lab or a police report - state the facts clearly and describe the situation completely. Don't describe things as "random" or "unusable" or "broken" - those terms are so broad they actually tell us very little, instead try to characterize the behavior as if you were studying the problem scientifically.

3. Avoid assuming that a bug you see on your system is seen by everyone on all systems; while some X bugs are widespread, the majority tend to be somewhat hardware-specific or even specific to some configuration that you've done. Indeed, there are relatively few bug reports about -fglrx open right now. Instead, try to think about what might make *your* system different than other people's - it can give strong clues as to what went wrong.

4. You've mentioned Alpha 3 specifically, which makes me wonder if you had successfully used fglrx on oneiric previously. If you have, and know a bug is a regression from an earlier point in time, it is very valuable to mention this; often in those situations we can look at what got upgraded when as a clue to finding the bug.

Hope this all helps, and good luck improving your bug report.