https://bugs.winehq.org/show_bug.cgi?id=39849
Bug ID: 39849 Summary: winepulse.drv is used while winealsa.drv is selected Product: Wine Version: 1.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: sworddragon2@aol.com Distribution: ---
In winecfg -> Audio the driver shown there as selected is winealsa.drv but on starting applications I'm often seeing the line "err:module:load_builtin_dll failed to load .so lib for builtin L"winepulse.drv": libpulse.so.0: cannot open shared object file: No such file or directory". libpulse0:i386 is not installed on my system and installing it would cause the error message to be replaced with "err:pulse:pulse_contextcallback Context failed: Connection refused". I think if PulseAudio is not used by the system for example because only ALSA is being used Wine should not try to use PulseAudio then.
https://bugs.winehq.org/show_bug.cgi?id=39849
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aeikum@codeweavers.com, | |austinenglish@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=39849
--- Comment #1 from Andrew Eikum aeikum@codeweavers.com --- Do you have the "Audio" driver setting set in your registry? If not, then we need to probe each type of audio driver to determine which is available. For winepulse, we try to load libpulse in order to contact the PA server.
If you really want to avoid this (why?), then you can set the Audio driver setting to "alsa", which will skip probing all of the available drivers. See http://wiki.winehq.org/UsefulRegistryKeys.
https://bugs.winehq.org/show_bug.cgi?id=39849
--- Comment #2 from sworddragon2@aol.com --- (In reply to Andrew Eikum from comment #1)
Do you have the "Audio" driver setting set in your registry?
No, the key doesn't exist.
(In reply to Andrew Eikum from comment #1)
If not, then we need to probe each type of audio driver to determine which is available. For winepulse, we try to load libpulse in order to contact the PA server.
Sounds plausible but if this probing is a normal behavior I would not expect to see an error if Wine finds out that a specific audio driver can't be used (except maybe if all probes are failing).
https://bugs.winehq.org/show_bug.cgi?id=39849
--- Comment #3 from Andrew Eikum aeikum@codeweavers.com --- (In reply to sworddragon2 from comment #0)
libpulse0:i386 is not installed on my system and installing it would cause the error message to be replaced with "err:pulse:pulse_contextcallback Context failed: Connection refused".
This error should no longer be printed. However the failure to load libpulse.so.0 will still be printed. We'd have to load the library dynamically, and I'm not sure it's worth that much effort to avoid printing the message.
commit 87754283becca7aef8f90af1d584d47ad25d8324 Author: Andrew Eikum aeikum@codeweavers.com Date: Mon Jul 25 13:00:14 2016 -0500
winepulse.drv: Downgrade failed server connection message to WARN.
https://bugs.winehq.org/show_bug.cgi?id=39849
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-6.5?