Mailinglist Archive: opensuse-factory (905 mails)

[Warren Stockton <wns@xxxxxxxxxxx>]

On Thursday 05 June 2008 05:50:52 John ffitch wrote:
> I just tried sound for the first time since installing RC1
>
> No sound.  Tried checking the state of muting etc with alsamixer and get
> the message
>
> *** PULSEAUDIO: Unable to connect: Connection refused
>
> alsamixer: function snd_ctl_open failed for default: Connection refused
>
>
> Is this expected?

I don't know  the answer to your question but I also see these errors.  I am 
not sure if it is due to a configuration error from routinely updating to 
factory for the past 10 months and might be corrected if I did a fresh 
install.

I use KDE3 and it appears the only thing that ever starts the pulsaudio 
daemon, is if I use amarok with the gstreamer engine, and then I get some 
sound with amarok.   As I normally use amarok/kaffeine with a locally 
compiled xine-lib, I don't get any sound.  

I ran:
# mv /etc/asound-pulse.conf /etc/asound-pulse.conf.XXX

Now alsamixer works...  Yast2 can test and adjust the volume and the KDE3 
sound system now provides sounds... and I no longer get error dialogs from 
kaffeine about not finding any audio drivers....

So my question(s) are:
Is "pulseaudio -D" supposed to be started by a bootscript or when logging in 
to the GUI via xdm/kdm/gdm? Or is one just supposed to gut out the pulseaudio 
configration when using KDE3?
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx