Created attachment 380714 [details] gdb-trace-file Description of problem: Ekiga is utilizing CPU extensively while idle (no active calls). Doing a File>exit and the process remains in the background. Have to manually kill the process. Version-Release number of selected component (if applicable): 3.2.6 How reproducible: initialize the program Additional info: SYSTEM: Linux dragon-lx 2.6.30.9-102.fc11.x86_64 #1 SMP Fri Dec 4 00:18:53 EST 2009 x86_64 x86_64 x86_64 GNU/Linux
This is being seen upstream as well
*** Bug 572063 has been marked as a duplicate of this bug. ***
On my system the high CPU usage only strats after accepting a call, perhaps due to pulseaudio issues. Why ship Fedora with pulseaudio when apps don't work with it?
(In reply to comment #3) > On my system the high CPU usage only strats after accepting a call, perhaps due > to pulseaudio issues. Quite possibly. > Why ship Fedora with pulseaudio when apps don't work with it? Well generally ekiga does work fine. I know of 100s of people using ekiga on Fedora with no issues. There's been fairly extensive testing of the issue. Its seen on more places than just Fedora and while a lot of testing has been done the precise problem has not been found. It works fine in the vast majority of situations. Unfortunately ekiga is a very complex app with a lot of legacy stuff. Add to the both the complexity of VoIP through things like firewalls and sound card latency issues the app has issues that can be at times very hard to recreate. If you can recreate it regularly and successfully try running ekiga from the command line using 'ekiga -d 4' and if the problem still happens attach the output as a text file. I am not a developer of ekiga. I merely somehow got landed with maintaining it as best as possible in Fedora because no one else wanted to. Look at the open bugs against it and see some of the complex issues there are open. Its not that I don't want to assist in the fixing of your issues. Its generally that I can't.
Created attachment 399665 [details] ekiga -d 5 log
Well generally ekiga doesn't work fine. It hasn't worked at all here. (not one succesfull call!) We have the multiple interface issue. We have this CPU issue. We have maybe a pulseaudio issue. And I saw that ekiga doesn't really accept a call when I click to do so. I attached a log. I disable usb0 first, else It won't work at all when i call, it won't ring. I start ekiga -d 5, call the number. I see the load go up when it rings. It does beep some sound for the ring. Then I click accept and nothing happens. Load stays at 100% for that core. I kill the program afterwards. Please fix this! If you ship the gnome 'suite' of software with troubles like this it is even worse than the years old (!) transparent icon issue in the gnome desktop.
Why didn't I mention the ^M's (CR) in the logfile? We are on unix and we don't use CR. Please fix.
Hi, @udo, I may have a fix for the call failure. Please, install this package: http://ekiga.net/yannick/f12/opal-3.6.6-1.1.fc12.x86_64.rpm Start Ekiga, Make sure the option "Edit->Preferences->General Settings->Disable Network Detection" is OFF (if you change it, please restart Ekiga) Then try to place a call. This package is OPAL 3.6.6 + this patch: http://opalvoip.svn.sourceforge.net/viewvc/opalvoip?view=rev&revision=24129 More packages (i686, debug, devel) and the source package here: http://ekiga.net/yannick/f12/ Best regards, Yannick
Installed Opal update. Started Ekiga. Set Disable Network Detection to OFF Stopped Ekiga Started Ekiga Placed call to Ekiga. Accepted call. No change w.r.t. CPU-hogging behaviour. Killing Ekiga after occuring this bug is hard.
Thank you for the test.
ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12
Ekiga now works after answering the phone! CPU consumption is still quite high (38% on AMD quadcore 2200 Mhz).
One weird observation: Starting Ekiga and calling it does not give me a RING. 2nd try same. So I stopped Ekiga. I started Twnkle, called myself and got a RING, answered, all OK. I quit Twinkle. I started Ekiga again. Called myself. RING and working OK. Why?
(In reply to comment #13) > One weird observation: > Starting Ekiga and calling it does not give me a RING. > 2nd try same. > So I stopped Ekiga. > I started Twnkle, called myself and got a RING, answered, all OK. > I quit Twinkle. > I started Ekiga again. > Called myself. > RING and working OK. > > Why? Please log a separate bug report. This is nothing to do with the above bug.
This was introduced after the most recent update. Need specific test/log etc?
(In reply to comment #15) > This was introduced after the most recent update. > Need specific test/log etc? Open a new ticket and we'll detail it there.
ekiga-3.2.7-1.fc12, opal-3.6.8-1.fc12, ptlib-2.6.7-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update ekiga opal ptlib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/ekiga-3.2.7-1.fc12,opal-3.6.8-1.fc12,ptlib-2.6.7-1.fc12
ekiga-3.2.7-1.fc12, opal-3.6.8-1.fc12, ptlib-2.6.7-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.