Description of problem: I only noticed this after the fact. But, I was changing network interfaces a lot lately, switching from WiFi to wired and back. May or may not be related to that. Version-Release number of selected component: ekiga-4.0.1-6.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 3 cmdline: /usr/bin/ekiga crash_function: SIPURL::SIPURL executable: /usr/bin/ekiga kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1002 Truncated backtrace: Thread no. 1 (10 frames) #0 SIPURL::SIPURL at /usr/src/debug/opal-3.10.10/src/sip/sippdu.cxx:234 #1 SIPRegisterHandler::CreateTransaction at /usr/src/debug/opal-3.10.10/src/sip/handlers.cxx:647 #2 SIPHandler::WriteSIPHandler at /usr/src/debug/opal-3.10.10/src/sip/handlers.cxx:360 #3 OpalTransportUDP::WriteConnect at /usr/src/debug/opal-3.10.10/src/opal/transports.cxx:1478 #4 SIPHandler::SendRequest at /usr/src/debug/opal-3.10.10/src/sip/handlers.cxx:273 #5 SIPHandler::ActivateState at /usr/src/debug/opal-3.10.10/src/sip/handlers.cxx:245 #6 SIPEndPoint::Register at /usr/src/debug/opal-3.10.10/src/sip/sipep.cxx:1096 #7 Opal::Sip::EndPoint::Register at ../lib/engine/components/opal/sip-endpoint.cpp:554 #8 Opal::Sip::subscriber::Main at ../lib/engine/components/opal/sip-endpoint.cpp:98 #9 PThread::PX_ThreadStart at ptlib/unix/tlibthrd.cxx:495
Created attachment 858228 [details] File: backtrace
Created attachment 858229 [details] File: cgroup
Created attachment 858230 [details] File: core_backtrace
Created attachment 858231 [details] File: dso_list
Created attachment 858232 [details] File: environ
Created attachment 858233 [details] File: exploitable
Created attachment 858234 [details] File: limits
Created attachment 858235 [details] File: maps
Created attachment 858236 [details] File: open_fds
Created attachment 858237 [details] File: proc_pid_status
Created attachment 858238 [details] File: var_log_messages
This is the same bug as https://bugzilla.redhat.com/show_bug.cgi?id=955075. As we plan to move soon to newer ptlib/opal, this bug will surely be fixed. So I suggest to simply wait the next major ekiga release (or its preliminary releases) to confirm that this crash in SIPURL do not appear anymore.
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.