It is generally the case that people who write error messages are at least
trying to be helpful (at least, I am when I write error messages). Occasionally they succeed, against the considerable odds, and the error message actually contains information that is actually useful in actually diagnosing the problem. So telling us:
"unable to display yada yadda yadda......"
may be rather less helpful than giving the real description of exactly what happened, including the exact text of the message, preferrable cut-and-pasted rather than retyped-with-a-few-errors.
(I once put some software out to some beta testers. This software put enough information in its error messages to pinpoint the problem to the exact line of code that was broken. So what did this ****** of a beta tester report to us? "Oh, there was some message about "internal error" and then some numbers ... no, sorry, I didn't bother to take any note of the numbers". Can't win, can you.)