abrt 1.0.0 detected a crash. How to reproduce ----- 1. Start ekiga. The account associated with ekiga is a Gizmo5 account. Perhaps any SIP account will do? 2. Log into Google Voice 3. Initiated a call through Google Voice to a landline, selecting the associated Gizmo account as the phone to take the call on 4. Click "Connect" 5. Google Voice reports "calling you" and attempts to dial the SIP number for the Gizmo account 5a. Sometimes, this works; Ekiga answers and the call connects. If the call connects, go to step 6. 5b. If there is no response, I repeat steps 3-5. There continues to be no response. During this step, Ekiga will crash sometimes. To be clear, it usually takes more than one failed attempt to call Ekiga before it crashes. 5c. I quit trying to connect and close Ekiga. During this step, Ekiga will crash sometimes. 6. End the call in Ekiga by clicking the "hang up" icon. 7. Try to initiate another call by repeating steps 3-5. Many times, if the first call is successful, the second call will not be. Comment: This crash doesn't occur consistenly, so these steps may not lead to a crash. However, in the instances that it did occur, the above is what I did. Attached file: backtrace cmdline: ekiga component: ekiga executable: /usr/bin/ekiga kernel: 2.6.31.6-145.fc12.i686 package: ekiga-3.2.6-1.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 377893 [details] File: backtrace
*** Bug 551388 has been marked as a duplicate of this bug. ***
Could someone please try yo recreate this crash by running ekiga with command line options of 'ekiga -d 4' to get debug output and please attach it too this bug as a text file.
Attached is the output of ekiga -d 4
Created attachment 388689 [details] Debug output Unlike in the case described above, ekiga does not outright crash. Instead, it simply hangs when either hanging up or trying to initiate a subsequent call. This debug output is from the latter situation.
Thanks for the update.
Is this reported to upstream ptlib/opal as well, and if so, can an external bug number be added for it?
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-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.