Not a bug but more a request for information on opensuse 11.2 with KDE 4.3.5
I always was under the assumption that opensuse/KDE used Alsa but I am getting a bit unsure about if this is fully true.
Recently under Wine I have been getting the following message: AL lib: Pulseaudio.c:386 Contect did not get ready: Connection refused.
Now Wine has been set to Alsa for a long time now so it confused me, I did a rpm search on what exactly is installed and came up with this:
alsa-devel-1.0.21-3.2.i586
alsa-utils-1.0.21-3.1.i586
alsa-oss-1.0.17-25.2.i586
alsa-1.0.21-3.2.i586
alsa-plugins-1.0.21-3.3.i586
libpulse0-0.9.21-1.2.1.i586
The first set I expected and sort of showed me I am running Alsa. The last one I did not expect, so I figured it might be the cause of the error under Wine so I tried to remove it but it seems its used by 125 other entries including kde-base. So not a good idea I figured. Looking at the file list:
/usr/lib/libpulse-simple.so.0
/usr/lib/libpulse-simple.so.0.0.3
/usr/lib/libpulse.so.0
/usr/lib/libpulse.so.0.12.2
/usr/lib/libpulsecommon-0.9.21.so
I figured I move these 5 files and do a reboot to see what happens, before the reboot KDE multimedia showed HDA Intel as output device, after the reboot it showed ALSA and OSS as output devices.
Interestingly enough the wine application no longer gives the AL Lib Pulseaudio error and almost all other programs like amarok or opera/youtube give sound, except mplayer with does not like the idea of not being able to access libpulse.so.0.
The error message itself : Pulseaudio.c:386 Contect did not get ready: Connection refused. Is I think because no pulse daemon is running, again pointing towards it being Alsa, So to me it seems Alsa is the primary sound system but somewhere in between libpulse.so.0 is used, is this for compatibility reason so there does not need to be an mplayer for also and one for pulse or why ?
So my question is what is the deal here ?
Thank you for enlightening me