Red Hat Bugzilla – Bug 441202
Ekiga crashes on startup
Last modified: 2018-04-11 11:28:03 EDT
Description of problem:
ekiga crashs on startup, apparently trying to get/process account details
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run ekiga from command line or menu
detailed backtrace attached
Created attachment 301466 [details]
Doesn't work at all for me either.
It seems to be related to pwlib rebuild with gcc-4.3. Downgrading to
pwlib-1.10.10-4.fc9.i386.rpm works for me.
Created attachment 302885 [details]
backtrace from starting Ekiga
And yes downgrade to pwlib-1.10.10-4.fc9.x86_64.rpm works for me as well.
Also crashes for me. See
I'm having a similar problem (see linked Gnome Bugzilla item). Judging by
similar reports, they won't look into it because 2.0.12 is available. Any idea
when this is going to be added into Fedora (rawhide/9)?
Seems that there is work going on on packaging 2.0.12, but the recent builds
failed. See Koji.
Yes, I checked Koji to see if there were any newer builds. However, I saw that
the last build was in March, hence my request as to whether any further builds
were in progress.
*** Bug 441767 has been marked as a duplicate of this bug. ***
this is bug on opal
Steps to resolve this bug:
1) rebuild & install opal-2.11*.src.rpm
2) rebuild & ekiga-2.0.11*.src.rpm
I went directly to the current F-9 branches of opal and ekiga, and did just
this, and the results are a working ekiga. Can we get this done for a zero-day
release? I'll be happy to visit bodhi and vote appropriately.
This would be great! I'm currently relying on Twinkle for my VoIP needs, and I'd
quite like Ekiga to work correctly (since it hasn't worked properly since Fedora 8!)
I can confirm that rebuilding OPAL and Ekiga from the source files works fine.
Ekiga is now working fine on my computer - thanks to Alexey and Paul for this.
opal-2.2.11-4.fc9 has been submitted as an update for Fedora 9
The new opal library successfully compiles against Ekiga 2.0.12 (source from
Ekiga website) and works with Ekiga 2.0.11 (recompiled from Fedora source RPMs).
Cheers to Paul for providing this update. Would it now be possible to submit a
working version of Ekiga to the repository?
I also rebuilt opal and ekiga and now have a working copy. Versions are
opal-2.2.11-3.fc9.i386 and ekiga-2.0.11-3.fc9.i386.
ekiga-2.0.12-2.fc9 has been submitted as an update for Fedora 9
opal-2.2.11-4.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
ekiga-2.0.12-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
I cannot find opal-2.2.11-4.fc9 in updates, only in koji. Can you verify, please?
According to Bodhi, both opal-2.2.11-4.fc9 and ekiga-2.0.12-2.fc9 have been
pushed into stable, so they should be available through the updater.
(In reply to comment #23)
> According to Bodhi, both opal-2.2.11-4.fc9 and ekiga-2.0.12-2.fc9 have been
> pushed into stable, so they should be available through the updater.
I know, but please look at:
New Ekiga is present, new opal is not.
Also in Koji, Ekiga is tagged dist-f9-updates, while opal is tagged
dist-f9-override and dist-f9-updates-testing.
Might be worth emailing Paul Frields as he was the one that packaged up the
updated Opal and Ekiga libraries (unless you have other "contacts" that could
It can take a couple days sometimes for them to be signed and pushed to the
mirrors. In the meantime, you can use the copies in koji.
Other 5 days have passed, but the opal updated package hasn't hit the mirrors.
BTW, the relative Fedora Update Notification came out correctly on 2008-05-13.
I know I can use the package in Koji, but this is not the solution for everybody!
*** Bug 447002 has been marked as a duplicate of this bug. ***
seems that there is something wrong with bodhi, the new opal isn't even here:
It was tagged for updates just recently. You'll probably find it in the repos
you are right, it is there now. but why did it take so long? is it normal or was
there some problem? thanks :)