ekiga hangs after x server restart

Thanks for your bug report. When you say ekiga is running do you mean you are in a conversation or that it is docked in the panel? What version of ekiga do you have installed? You can check with 'dpkg -l ekiga' in a terminal.

it is just docked in the panel.

the version i am running is 2.0.3-0ubuntu3.

Is ekiga using resources a lot after you log in again or when no one is logged in? Thanks in advance.

after i relogin i can see that ekiga consumes one of my cores computing power.

i just looked if ekiga locks(consumes my cpu power) already before logging in. it doesn't. but when i logged in then it wasn't locked and the window of ekiga came up which doesn't otherwise. i have ekiga in autostart. so it seems to depend on how fast I do the relogin...

I believe I can reproduce this in Debian 4.0 (and in Ubuntu 6.06). I didn't have to actually zap my X server; just closing the ekiga window with Alt+F4 is enough to leave the instance running in the background. It will start spinning at 100% CPU after logout.

Are you able to test if this problem occurs with ekiga in gutsy? The gutsy release contains a new ekiga which fixes a lot of problems.

seems to me it is already fixed in feisty. at least i can't reproduce it anymore...

Ok thanks I will close the bug then.

i am reopening because the bug is back in gutsy....

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Intrepid Ibex. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

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!