Bug 674573

Summary: [abrt] ekiga-3.2.7-4.fc14: SIPEndPoint::GetLocalURL: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jan Teichmann <jan.teichmann>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bobkaiser1, djo2, pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:422aec4cb1ab112a4be7f3f60b5cd5cd7299a4fb
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:01:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Jan Teichmann 2011-02-02 14:40:07 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: ekiga -d 5
component: ekiga
crash_function: SIPEndPoint::GetLocalURL
executable: /usr/bin/ekiga
kernel: 2.6.35.10-74.fc14.i686
package: ekiga-3.2.7-4.fc14
rating: 4
reason: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296657137
uid: 500

How to reproduce
-----
tried to establish an echo test call to 500
first came a "security check failed message"
and then ekiga crashed
Comment 1 Jan Teichmann 2011-02-02 14:40:09 UTC 
Created attachment 476582 [details]
File: backtrace
Comment 2 Peter Robinson 2011-02-02 15:19:59 UTC 
Can you run ekiga from the command line using the following "ekiga -d4" to recreate the problem and the save the output to a text file and attach it to this bug report.
Comment 3 djo2 2011-04-10 18:02:19 UTC 
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.ouverture de Ekiga
2.tentative de communication avec un contact
3.
Comment 4 abrt-bot 2012-03-21 16:52:26 UTC 
*** Bug 704706 has been marked as a duplicate of this bug. ***
Comment 5 Fedora End Of Life 2012-08-16 15:02:00 UTC 
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping