Bug 618499

Summary: [abrt] crash in ekiga-3.2.7-3.fc13: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: jasonbenedict
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:5bf5fdbf5d428fb55c991119afcf8f8e1fc0f06f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 19:55:43 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

Description jasonbenedict 2010-07-27 05:13:49 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: ekiga
comment: I started ekiga, configured to connect to my IPPBX, to make calls. after a 1mins or so talk i hang up. Then i proceed to do email via thunderbird, leaving ekiga docked. After a while, thinking i will not be using it, i quit ekiga. Then, this message appeared.
component: ekiga
executable: /usr/bin/ekiga
global_uuid: 5bf5fdbf5d428fb55c991119afcf8f8e1fc0f06f
kernel: 2.6.33.6-147.fc13.x86_64
package: ekiga-3.2.7-3.fc13
rating: 3
reason: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. start it.
2. made some phone call
3. exit
Comment 1 jasonbenedict 2010-07-27 05:13:52 UTC 
Created attachment 434597 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:55:43 UTC 

*** This bug has been marked as a duplicate of bug 612130 ***
Comment 3 Karel Klíč 2010-11-08 19:55:43 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #612130.

Sorry for the inconvenience.