Bug#378846: Still valid?

[Eugen Dedu]

Teemu Ikonen wrote:
> On Wed, Jun 17, 2009 at 7:28 PM, Eugen
> Dedu<Eugen.Dedu at pu-pm.univ-fcomte.fr> wrote:
>> Teemu Ikonen wrote:
>>> I then upgraded to version 3.2.1~git20090515.9d0263-1 from testing and got
>>> no
>>> sound output at all during calls. Microphone input works (i.e. the bar
>>> moves in
>>> the Audio Settings dialog during calls) but sound output does not.
>>> Interestingly, sound events work when tested from the preferences dialog,
>>> except for the 'new instant messages' sound, which plays, but brings up an
>>> 'Error while opening audio output device' dialog. This happens with all
>>> the
>>> sound devices ekiga lists in this system (Default, HDA Intel, HDA Intel
>>> (1)).
>> Do you have audio codecs checked on in Preferences?
> 
> Yes.
> 
>> Please send the output when doing a call and there is no sound:
>> $ ekiga -d 4 2>output

Hi Teemu,

I am really sorry for the delay of this e-mail.  I would like to fix
this bug now.

I do not see any problem in your output.  Please explain more what does
"sound output does not work" mean.  During a call, the call is
established, the audio (and video) codec is shown near the image, the
other endpoint hears you, but you canot hear the other endpoint?  Does
audio output work when you call 500 at ekiga.net?  Maybe your sound card
has the output set to zero?!  During these tests, please check off the
CELT audio codec.

Note that with 3.2.6 the newmessage.wav file playing was fixed.  If
possible, use that version (in debian unstable).

-- 
Eugen