Upgrade to Intrepid causes ekiga to not detect sound device

[Ian Clark]

I upgraded from Hardy to Intrepid, and suddenly my mic was not detected anymore. Running "amixer set 'Capture' cap" was the only way to get the mic detected (GUI methods didn't work) in other apps, but Ekiga still will not detect it.

When running the druid I got the following error message when hitting "test" for audio:
"Failed to open the device
Impossible to open the selected audio device (Default) for playing. Please check your audio setup, the permissions and that the device is not busy."

1. Skype detects the mic, as does Audacity and Voicerecorder
(had to run "amixer set 'Capture' cap" to get this running)
2. When running Ekiga in terminal, the following error is given:
ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.default
Segmentation fault
3. Though Skype detects the mic, it still gives a similar error in terminal:
ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
4. pulseaudio and jackd are not installed

[Yannick Defais (sevmek)]

Hi,

Ubuntu Jaunty ships with a new Ekiga (3.2.0) which fix numerous bugs.

Is this bug still valid using it?

Best regards,
Yannick

[Ian Clark (blacktuzi)]

Sound is still broken. The two audio sliders are dead. I have two choice for audio input and output: default and IntelICH5. No combination of these works. Main audio device only has one choice: ALSA. The video image has strange color and cannot be adjusted, either.

[Yannick Defais (sevmek)]

Ok, let's take issues one at the time. First audio.

In ubuntu jaunty, do you have any feedback from ekiga about the audio?

Please use "default" for ringing, output and input in ekiga preferences.

The sliders in Ekiga for audio only are enabled during a call, use the roster and call the echo test, then use the sliders in the call panel.

If it is not enough to have sound working, please attach a debug output using this command:
$ ekiga -d 4 2>output.txt

Best regards,
Yannick

[Ian Clark (blacktuzi)]

I just found out I'm still on 2.0.12. How do I add the repository source to test the new Ekiga? I'm on 8.10, as it says in the bug report. I tried getting some feedback about audio, but nothing. I can't hear myself. I suppose I'd have to find someone to call to try it out. I remember from before that it doesn't work. My screen name is KunikloNigra if you want to add me.

[Yannick Defais (sevmek)]

Hi,

Could you try a live CD of Ubntu Jaunty (9.04)? There is an echo test available by default in the main GUI if you have an account on ekiga.net.

Unfortunately there is no official way to have ekiga 3.x on ubuntu intrepid (8.10).

Best regards,
Yannick

[Ian Clark (blacktuzi)]

I misread your meaning there, sorry about that. You're idea is to test Jaunty. I've heard good things about audio in Jaunty, but not 100%. I'm scared to "upgrade" again. I used to have perfect audio in 8.04. I don't know if moving to 9.04 will do that. My audio drivers should be ice1724 or intel8x0. 8.10 has been a real mess for me.

[Ian Clark (blacktuzi)]

OK I'm downloading 9.04 (gnome) and will give it a try from a live CD. I have Kubuntu 9.04 and sound worked out well with it after all the updates. I can even edit video (!) and have sound while I edit. Crazy stuff. I'd like to try a Gnome version anyway because I think Kdenlive will work fine on it, and it will support Chinese input better.

[Leo Arias (elopio)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Is this still an issue for you? Thanks!

[Ian Clark (blacktuzi)]

I no longer use Intrepid nor Ekiga (and not even skype). Google chat
seems to do video fine.

Thanks!

Ian

On 10/23/10, Leo Arias <email address hidden> wrote:
> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Is this still an issue for you? Thanks!
>
> --
> Upgrade to Intrepid causes ekiga to not detect sound device
> https://bugs.launchpad.net/bugs/355585
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “ekiga” package in Ubuntu: Incomplete
>
> Bug description:
> I upgraded from Hardy to Intrepid, and suddenly my mic was not detected
> anymore. Running "amixer set 'Capture' cap" was the only way to get the mic
> detected (GUI methods didn't work) in other apps, but Ekiga still will not
> detect it.
>
> When running the druid I got the following error message when hitting "test"
> for audio:
> "Failed to open the device
> Impossible to open the selected audio device (Default) for playing. Please
> check your audio setup, the permissions and that the device is not busy."
>
> 1. Skype detects the mic, as does Audacity and Voicerecorder
> (had to run "amixer set 'Capture' cap" to get this running)
> 2. When running Ekiga in terminal, the following error is given:
> ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.default
> Segmentation fault
> 3. Though Skype detects the mic, it still gives a similar error in terminal:
> ALSA lib pcm.c:2202:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
> 4. pulseaudio and jackd are not installed
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/355585/+subscribe
>

--
陶氏哲學服務

[Mihail Fontul (mihailfontul)]

All,

I am not using Ekiga anymore. Thanks.

2010/10/23 Leo Arias <email address hidden>

> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Is this still an issue for you? Thanks!
>
> --
> Upgrade to Intrepid causes ekiga to not detect sound device
> https://bugs.launchpad.net/bugs/355585
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mihail Fontul

[Leo Arias (elopio)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!