After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 346403 - Sound error when calling in
Sound error when calling in
Status: RESOLVED DUPLICATE of bug 329015
Product: ekiga
Classification: Applications
Component: general
2.0.x
Other All
: Normal major
: ---
Assigned To: Snark
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-02 16:25 UTC by Florian
Modified: 2006-08-25 17:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Florian 2006-07-02 16:25:20 UTC
Please describe the problem:
I have a sipgate.de account. When I ring myself from landline to ekiga and  hit the answer button, I receive the message, that my driver is not full duplex capable. I am running Ubuntu 6.06.

Steps to reproduce:
1. start ekiga
2. call my sip-number from landline
3. hit the answer button in ekiga



Actual results:
message appears saying audio hardware is not full duplex capable or other program is using the sound hardware

Expected results:
no such message appears and sound is working

Does this happen every time?
yes

Other information:
I hope this helps, if you need more information I would be more than happy to give it to you.
Comment 1 Snark 2006-07-03 05:51:35 UTC
My guess is that you're using the OSS plugin, which may have full-duplex issues.

Install and use the ALSA plugin.
Comment 2 Damien Sandras 2006-07-03 08:11:04 UTC
Or the soundcard is already busy.

I really think it is a configuration issue and not a bug.
Comment 3 Florian 2006-07-03 17:09:44 UTC
This is what I get when I do:

cat /dev/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.10rc3 emulation code)
Kernel: Linux Gurke 2.6.15-25-386 #1 PREEMPT Wed Jun 14 11:25:49 UTC 2006 i686
Config options: 0

Installed drivers:
Type 10: ALSA emulation

Card config:
NVidia nForce2 with ALC650F at 0xe8081000, irq 193
MPU-401 UART at 0x330, irq 10
USB Device 0x471:0x311 at usb-0000:00:02.0-2, full speed

Audio devices:
0: NVidia nForce2 (DUPLEX)
2: USB Audio

Synth devices: NOT ENABLED IN CONFIG

Midi devices:
1: MPU-401 UART MIDI

Timers:
7: system timer

Mixers:
0: Realtek ALC650F
1: mixer10
2: USB Mixer

In the audio device section of ekiga, the alsa plugin is enabled, no other choices are available. Is it due to Ubunut 6.06?
Comment 4 Snark 2006-07-03 19:03:11 UTC
I'm using ubuntu 6.06.

Does it work when you call sip:500@ekiga.net ?
Comment 5 Damien Sandras 2006-07-03 21:22:55 UTC
And are you sure ESD or ARTSD or whatever is not already using the soundcard?
Comment 6 Florian 2006-07-04 06:32:51 UTC
I called 500@ekiga.net:
ekiga reported: security check failed.

I found a checkbox in ubuntus audio configuration saying software mixing of system sounds (ESD). I disabled this, now it works. But I cannot hear the system sounds anymore. Is this the wanted behaviour?
Comment 7 Snark 2006-07-04 07:38:18 UTC
Blah... if you disable system sounds, you don't hear system sounds : that is the normal behaviour.

If you enable it though, you should hear system sounds *and* ekiga should pause it correctly ; at least ekiga does what it takes so things happen this way. Unfortunately, we have issues with esound, which make things less bright : it basically doesn't work reliably.

I hate esound. Kill it, kill it, kill it.
Comment 8 Florian 2006-07-04 14:44:39 UTC
Sorry, probably I did not write clearly what I meant. Of course I cannot hear system sounds anymore, when I disable them.:)

But is it wanted by ekiga, that I have to disable system sounds so ekiga is working?

Anyway, do you need more information? Can I help somehow? Otherwise I would stop here. 
Comment 9 Snark 2006-07-04 16:08:00 UTC
Well, I haven't been very clear either :-)

Ekiga stops esound when a call begins. In such a situation, esound is supposed to be stopped. For unknown reasons, it isn't. We have no idea why.

We do the right thing in ekiga ; esound is the problem...
Comment 10 Snark 2006-08-25 17:28:06 UTC
Well, this problem is like #329015 : there is something very wrong which happens with esound and we don't know what. Marking this one as duplicate.

*** This bug has been marked as a duplicate of 329015 ***