Bug 572063

Summary:	Ekiga not pulseaudio compatible
Product:	[Fedora] Fedora	Reporter:	udo <udovdh>
Component:	ekiga	Assignee:	Peter Robinson <pbrobinson>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	12	CC:	pbrobinson
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-10 16:01:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description udo 2010-03-10 07:10:49 UTC

Description of problem:
Ekiga not pulseaudio compatible

Version-Release number of selected component (if applicable):
ekiga-3.2.6-1.fc12.x86_64

How reproducible:
Install or upgrade to Fedora 12.
Install ekiga.
Get inbound call.
See message about inability to open soundcard.

Steps to Reproduce:
1. See above
2.
3.
  
Actual results:
Inability to use soundcard

Expected results:
Working situation w.r.t. soundcards

Additional info:
This makes Ekiga unusable. 100% fail.

Comment 1 Peter Robinson 2010-03-10 07:25:36 UTC

ekiga works fine using alsa pulseaudio support. There is native support planned for the next release.

Comment 2 udo 2010-03-10 08:47:15 UTC

Sure, but it doesn't work for me.
Ekiga sees call, is set for default soundcards, accepts call and task hangs (100% cpu, ekiga responds badly, does not pick up call after instructed to do so).

So what is wrong?
Stock alsa config...

Comment 3 udo 2010-03-10 14:04:12 UTC

The previous comment is 100% reproducible. Any workarounds?

Comment 4 udo 2010-03-10 14:08:07 UTC

I do get the sip.xs4all.nl voicemail saying that the user I am calling (myself) is unreachable after this happens.

Comment 5 Peter Robinson 2010-03-10 16:01:07 UTC

Its a known issue from upstream. It needs to be fixed upstream. There are tickets tracking it but the progress isn't fast.

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

Comment 6 udo 2010-03-10 16:18:08 UTC

Are you VERY sure that a hanging ekiga is the same as (whatever) bug you think was mentioning this before?
In my issue the CPU usage ONLY starts when a call is received.
NONE of that is mentioned in teh bug you refer to.
Even if these bugs are present and progress is slow, Fedora does nothing.
It ships.
It does not fix, nor uses alternatives that work nor warn users about issues.