Many time someone has commented "I don't know why this build is failing!", and a quick search for "Error" in the build log reveals the exact cause.
My current pet peeve is an error message that reads "This application requires <dependency A>. <Dependency A> can be installed from <url>". If I had $1 for every time someone said "I don't know how to fix this".
You are not alone.
You can write your program so that on error it shows a message like:
"Push the red button"
... and many users will just stare at the screen and proclaim "I don't know what to do, what's wrong with it? How do I get back to the thing?"
I wanted to make sure it's not me who's using the terminal that's different, but it's not the case, bash's doc state that "Ctrl+F: Forward one character".
But this reasoning makes a lot of sense for the ones I get from people that definitely know copy-and-paste. For these folks, I get a screenshot and/or text of the error but still the "its broken" without much else.
Thus, it's not laziness, just something that logically follows from the erroneous assumption that there is only one kind of error, and thus, a competent programmer should automatically know the one solution to it.
* In terms of people not being able to copy-and-paste...just because they can do it in Word doesn't mean they realize that function exists in other apps. Take Google's finding that 90% of users didn't know how to use Ctrl-F (http://www.theatlantic.com/technology/archive/2011/08/crazy-...)....just a couple days ago, in the final week of my programming class, one of my students was amazed when I did a Ctrl-F in the terminal.