How to reproduce:
- Encounter a bug.
- Collect all the information you can find about the bug - how to reproduce it, what state the system was in, logs, crash dumps, versions, similar bugs, etc.
- Submit this information to the relevant forum, with a statement clearly indicating that you’d be willing to debug this further if simply given some hint as to how that could be done.
Expected results: At least one answer including one or more of the following:
- A pointer to an existing and relevant bug report you had missed.
- Instructions for gathering more information about the issue so that it can be properly researched and thus actually resolved for everyone.
- A dismissal of the issue because an assumption was fundamentally flawed (for example, it’s actually a feature or it can’t be fixed within this universe).
Actual results: Two answers:
- One suggesting to either restart, reboot or reinstall the system or supporting systems, all the way up to completely rebuilding the system from scratch “to see if it happens again.”
- Another one suggesting to upgrade to the latest version with no justification.
Additional information: When pointing out the problem of treating the symptom rather than the sickness in the long run the very notion is usually ridiculed or ignored.
As a full-time software developer and open source enthusiast I want to help fix problems in the programs I use rather than retrying until it all seems to work in my very specific situation. After all, others may be having the same issue, or I might encounter the same problem again. However, many of these programs are written in unfamiliar ways or languages, and there are people who are in a much better situation to fix them if I could only gather enough information to submit a useful bug report. I have tried in various ways and failed, so my question is this: