On 08/07/2009 06:49 PM, Colin Guthrie wrote:
'Twas brillig, and Patrick Shirkey at 07/08/09 07:41 did gyre and gimble:
yum install alsa-plugins-pulseaudio.i586

First off do you have a 32 bit system or is this a 32 bit library on a predominantly 64 bit system?



I have Fedora 11 64 bit with a dev version of pulse. I have both the 32 and 64 bit version of the alsa-plugins-pulseaudio library but skype and flash are not able to find the 64 bit version. Hard linking it from /usr/lib64 to /usr/lib doesn't do anything.


I enabled mails to my address from the mailing list now so no need to cc.


Patrick Shirkey
Boost Hardware Ltd





- I get the same error messages with skype and while playing youtube videos in firefox:

socket(): Address family not supported by protocol
ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect: Connection refused

- I have added my user as a member of the pulse group.

The groups should be irrelevant unless you are running in System Wide mode (which I suspect you are not - it's certainly not the recommended or default way on Fedora).

This happens when the libpulse client cannot connect to the server you are running. Simple tests are using:

paplay /usr/share/sounds/startup3.wav
aplay /usr/share/sounds/startup3.wav

This tests a native client and an alsa client using the alsa libraries.

What I suspect is happening here is that you are running a 64 bit system and that the above two commands will work fine.

However, the 32 bit libpulse that is installed on your system is looking for a different location to communicate with pulseaudio server (this *has* changed between 0.9.15 and 0.9.16).

It should just be a matter of building a 32 bit version of libpulse to go with your git master version.

If I'm wrong with the assumptions please let us know :)





Please cc me on the response.

Gmane, Gmane, Gmane :p


_______________________________________________
pulseaudio-discuss mailing list
pulseaudio-discuss@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss

Reply via email to