Bug 593864

Summary: [abrt] crash in ekiga-3.2.6-1.fc12: std::_Rb_tree_increment: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Fabrício <f_cabeca>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: pbrobinson
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:887d75ba4659e7c3aa35a4e9e719c6f4fb51d14f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-23 21:22:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
File: backtrace none

Description Fabrício 2010-05-19 21:43:56 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: ekiga
component: ekiga
crash_function: std::_Rb_tree_increment
executable: /usr/bin/ekiga
global_uuid: 887d75ba4659e7c3aa35a4e9e719c6f4fb51d14f
package: ekiga-3.2.6-1.fc12
rating: 4
reason: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Turned off ekiga after problems with SIP not working

Comment 1 Fabrício 2010-05-19 21:43:59 UTC
Created attachment 415270 [details]
File: backtrace

Comment 2 Peter Robinson 2010-05-23 21:22:19 UTC

*** This bug has been marked as a duplicate of bug 539541 ***