https://bugs.winehq.org/show_bug.cgi?id=49284
--- Comment #4 from Zebediah Figura z.figura12@gmail.com --- (In reply to Bart from comment #3)
(In reply to Zebediah Figura from comment #1)
We should probably avoid printing ERR messages in such cases, but that's often more work than its worth.
At my side, I would appreciate it a lot if messages like ERR and FIXME were avoided. ERR and FIXME messages give me the feeling that something didn't go well. Also, if these messages are avoided, the remaining messages should probably be included with a bug report. I no longer have to scratch behind my ear and wonder which messages should be included and which not.
With the exception of winediag messages, you should probably never pay attention to terminal output unless you're interested in debugging, and even then it's wise to ask a developer before assuming a message is relevant, because it usually isn't. Simply put, terminal output is pretty much entirely for debugging and shouldn't be paid any attention otherwise.
Of course it's accurate that ERR/FIXME implies something might be broken, but usually things break in a way that doesn't affect a given application. That doesn't mean it's not still broken...