http://bugs.winehq.org/show_bug.cgi?id=24569
--- Comment #10 from Jase Whipp jason.whipp@gmail.com 2010-09-30 12:37:40 CDT --- (In reply to comment #8)
(In reply to comment #7)
Once again: Wine doesn't write anything to ~/.xsession-errors, all Wine output is printed to stderr.
You need to find out who redirects Wine output to ~/.xsession-errors, and file a bug report to its developers.
Regarding WINEDEBUG usage refer to the user documentation, or ask on the user support forum.
IIUC, X automatically redirects stderr->xsession-errors if the program was not opened from a terminal.
That's my understanding as well.
I'm basically turning off a useful X log facility or disabling output for ALL wine apps which I shouldn't need to do for one chatty app. There's nothing broken in the X configuration. I still think an option in winecfg is warranted, that way a program that has too much sdout can be -all logged while others can be left alone with out creating pipe files.
And the issue of the fixme:tapi are way to numerous, I don't see how that's invalid.