I agree on almost everything you've written, but, getting the general userbase to understand this is... a challenge - the best we get is generally of the form:

I agree on almost everything you've written, but, getting the general userbase to understand this is... a challenge - the best we get is generally of the form: "It's crashing when I press this button", and a stacktrace (but that is thanks to the bug report feature). My product have both a supporter and a product manager interacting with the customers, and they generally file the bug reports. They have the contact with the customer and try their best to fill out as much as possible. That said, they're not developers and every now and then they cut the corner and need to be reminded that "I cannot press this button" is not good enough - unless the error is sporadic, always, and I really mean always, include a step by step guide to reproduce and include any files or input that might be needed, and double check that it's causing the error.