Hide Forgot
Description of problem: Clicked on Edit -> Accounts -> then Ekiga crashed Version-Release number of selected component: ekiga-4.0.1-6.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: ekiga crash_function: SIPURL::SIPURL(PString const&, OpalTransportAddress const&, unsigned short) executable: /usr/bin/ekiga kernel: 3.11.10-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 SIPURL::SIPURL(PString const&, OpalTransportAddress const&, unsigned short) at /lib64/libopal.so.3.10.10 #1 SIPRegisterHandler::CreateTransaction(OpalTransport&) at /lib64/libopal.so.3.10.10 #2 SIPHandler::WriteSIPHandler(OpalTransport&, bool) at /lib64/libopal.so.3.10.10 #3 OpalTransportUDP::WriteConnect(bool (*)(OpalTransport&, void*), void*) at /lib64/libopal.so.3.10.10 #4 SIPHandler::SendRequest(SIPHandler::State) at /lib64/libopal.so.3.10.10 #5 SIPHandler::OnTransactionFailed(SIPTransaction&) at /lib64/libopal.so.3.10.10 #6 SIPEndPoint::OnTransactionFailed(SIPTransaction&) at /lib64/libopal.so.3.10.10 #7 SIPTransaction::SetTerminated(SIPTransaction::States) at /lib64/libopal.so.3.10.10 #8 SIPTransaction::OnTimeout(PTimer&, long) at /lib64/libopal.so.3.10.10 #9 PTimerList::Process() at /lib64/libpt.so.2.10.10
Created attachment 840204 [details] File: backtrace
Created attachment 840205 [details] File: cgroup
Created attachment 840206 [details] File: core_backtrace
Created attachment 840207 [details] File: dso_list
Created attachment 840208 [details] File: environ
Created attachment 840209 [details] File: exploitable
Created attachment 840210 [details] File: limits
Created attachment 840211 [details] File: maps
Created attachment 840212 [details] File: open_fds
Created attachment 840213 [details] File: proc_pid_status
Created attachment 840214 [details] File: var_log_messages
Christian, I need an output of "ekiga -d 4 2>output" when ekiga crashes. This is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=955075.
(Un)fortunately this is not 100% reproducible. But I'll try to start Ekiga the way you described from now on and see if it catches anything. Thanks.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.