GNOME Bugzilla – Bug 583864
Cannot call anywhere
Last modified: 2009-07-06 12:41:56 UTC
Please describe the problem: It broke fatally with the latest Fedora-11 build: ekiga-3.2.4-1.fc11.x86_64 opal-3.6.2-1.fc11.x86_64 ptlib-2.6.2-1.fc11.x86_64 http://koji.fedoraproject.org/koji/buildinfo?buildID=102845 http://koji.fedoraproject.org/koji/buildinfo?buildID=102815 http://koji.fedoraproject.org/koji/buildinfo?buildID=102794 Steps to reproduce: 1. type sip:500@ekiga.net into the location bar. 2. click the green phone. Actual results: location bar changes and displays: pc:udp$ekiga.net:5060 red phone gets enabled after clicking red phone Ekiga completely hangs - unresponsive UI. Expected results: Start hearing ekiga.net echo. Does this happen every time? Yes. Other information: Also I see no accounts would be logged in, nothing happens when I enable them.
Please provide more information. I only have Debian to test, and it works on Debian.
The first problem is that your accounts are not registered. Could you send us a -d 4 output (ekiga -d 4 2>outFile)?
After trying to disable/enable the accounts it became no longer reproducible. Thanks for the debugging hint but I have to close it now. But it was reproducible many times before. I have 4 accounts enabled.
Got it reproducible again. It may be related with downgrades/upgrades back and forth ekiga-2.0.12 <-> ekiga-3.2.4.
Created attachment 135671 [details] -d 4 output.
Created attachment 135672 [details] ifconfig output As there were some problems with choosing the right interface (tun0 and no STUN) attaching also the `ifconfig' output.
Created attachment 135674 [details] Screenshot of checked accounts with no state message.
Jan, what is now the problem? Please reexplain what is the problem for files in comments #5 to #7. Is that no account is registered AND that UI is unresponsive when you press the green button, as you stated in the initial bug? Because I see in comment #5 that ekiga.net account gets registered, for example. I try to understand the registration issue, not the freeze (for the moment).
(In reply to comment #8) > Is that no account is registered AND that UI is unresponsive when you press the > green button, as you stated in the initial bug? Yes. > Because I see in comment #5 > that ekiga.net account gets registered, for example. From the Joe user POV I believe it is NOT registered. I see no accounts to be registered in the Accounts window according to their message/status.
This bug sounds the same as https://bugzilla.redhat.com/show_bug.cgi?id=505583
May I ask how many codecs are enabled? I remember I saw the call-and-freeze situation when I had too many codecs : since the list is too big, we end up stuck.
I have this bug too, except that it does not freeze. In my case, it has nothing to do with number of codecs enabled.
Eugen: does trunk work?
Yes.
Jan, could you test with current stable branches, see http://wiki.ekiga.org/index.php/Download_Ekiga_sources ? For me it is fixed...
(In reply to comment #15) > Jan, could you test with current stable branches, see > http://wiki.ekiga.org/index.php/Download_Ekiga_sources ? For me it is fixed... Already the Comment 0 bugreport was against these versions. Tried the upgrade now and the problem is not reproducible this time, closing it.
I wanted to say stable git branches, not tarballs. So you have just used git/svn branches or tarballs?
I always used the Fedora rpm packages. I have seen the bug only several times around Ekiga 2<->3 upgrades/downgrades, it is not reproducible for me now and I do not know how to make it reproducible. Not sure what I can do more.
Ok, thanks. I feel that this bug was fixed a few days ago, because I had it before more or less. Please open another bug report if still applies with the new coming 3.2.5 (in a very few days).