Description of problem: Whenever I run a binary via wine, I get the following message on stdout: Running padsp as pulseaudio wrapper for wine This is annoying for me because I make a lot of use of w32 console apps, and use their standard output. For example, I have an autoconf-like test similar to: $ cat test.c int main(void) { printf("#define SIZEOF_INT %d\n", sizeof(int)); } $ cl test.c $ ./test.exe > myheader.h myheader.h subsequently fails to compile because the pulseaudio output ends up there. If this output went to stderr (with all other wine output), things would work correctly. Version-Release number of selected component (if applicable): wine-core-0.9.52-2.fc8 How reproducible: Always. Steps to Reproduce: 1. $ wine > out 2>err Actual results: $ cat out Running padsp as pulseaudio wrapper for wine $ cat err Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --version Output version information and exit Expected results: All /usr/bin/wine output ends up in 'err'.
I know that this situation is not really nice but I think the reasoning for having wine report that it is using an ugly hack to make use of pulseaudio is ok at least for now till there is a better solution. Since this is _not_ an error message but just a reminder I think it should go to stdout instead of stderr. You can avoid this behavior if you e.g. call wine_bin directly. I am always open for other suggestions so
If I write a "Hello world" application, and run it, I expect it to print "Hello world" and nothing else. Having it print some garbage about pulseaudio counts as a bug to me. Running wine_bin is not an option because I run the binary directly, i.e. via binfmt_misc, which is set up in /etc/init.d/wine to use /usr/bin/wine, not wine_bin. All other wine debugging stuff (for example, complaints about the timezone, fixme:ntdll warnings, fixme:winspool warnings, etc.) goes to stderr, so does not interfere with the program itself.
In bug#429420 I asked to remove the "echo" statement from /usr/bin/wine, which solves the problem. And YES, I too think that this is a BUG, since it breaks other things around wine. Printing to stderr could be more acceptable.
wine-0.9.54-1.fc8, wine-docs-0.9.54-1.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update wine wine-docs'. You can provide feedback for this update here: http://admin.fedoraproject.org/F8/FEDORA-2008-1066
Just removing the "echo" line would have suffice. Anyway, I think that the ESound solution is the best.
wine-docs-0.9.54-1.fc7, wine-0.9.54-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
wine-0.9.54-1.fc8, wine-docs-0.9.54-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
> Anyway, I think that the ESound solution is the best. I agree. IMHO the padsp hack was a bad idea anyway. WINE should default to ESD for sound output, that way it will output to PulseAudio natively without wrapper hacks. As PulseAudio is the default sound solution in Fedora, the default WINE configuration should be the ESD backend.