Bug 1060532

Summary: [abrt] ekiga: SIPURL::SIPURL(): ekiga killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Paul DeStefano <prd-fedora>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: eugen.dedu, fukidid, info, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9b39232663f00034fd21fe1ddf3450bc544ab658
Whiteboard: abrt_hash:73713cbf4fa392ed2bc331a3194a74119157ae23
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:56:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Paul DeStefano 2014-02-02 11:40:21 UTC 
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
Comment 1 Paul DeStefano 2014-02-02 11:40:27 UTC 
Created attachment 858228 [details]
File: backtrace
Comment 2 Paul DeStefano 2014-02-02 11:40:30 UTC 
Created attachment 858229 [details]
File: cgroup
Comment 3 Paul DeStefano 2014-02-02 11:40:32 UTC 
Created attachment 858230 [details]
File: core_backtrace
Comment 4 Paul DeStefano 2014-02-02 11:40:34 UTC 
Created attachment 858231 [details]
File: dso_list
Comment 5 Paul DeStefano 2014-02-02 11:40:36 UTC 
Created attachment 858232 [details]
File: environ
Comment 6 Paul DeStefano 2014-02-02 11:40:39 UTC 
Created attachment 858233 [details]
File: exploitable
Comment 7 Paul DeStefano 2014-02-02 11:40:41 UTC 
Created attachment 858234 [details]
File: limits
Comment 8 Paul DeStefano 2014-02-02 11:40:44 UTC 
Created attachment 858235 [details]
File: maps
Comment 9 Paul DeStefano 2014-02-02 11:40:46 UTC 
Created attachment 858236 [details]
File: open_fds
Comment 10 Paul DeStefano 2014-02-02 11:40:48 UTC 
Created attachment 858237 [details]
File: proc_pid_status
Comment 11 Paul DeStefano 2014-02-02 11:40:50 UTC 
Created attachment 858238 [details]
File: var_log_messages
Comment 12 Eugen Dedu 2014-02-12 17:37:11 UTC 
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.
Comment 13 Fedora End Of Life 2015-05-29 10:46:39 UTC 
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.
Comment 14 Fedora End Of Life 2015-06-29 14:56:19 UTC 
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.