Bug 661446

Summary: [abrt] gq-1.3.4-9.fc13: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Adam Carbone <acarbs12>
Component: gqAssignee: Terje Røsten <terje.rosten>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:30788511ec55ba1abb1a9a7de0dc03c3b3577e78
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-17 15:12:03 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 Adam Carbone 2010-12-08 19:28:54 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: gq
component: gq
executable: /usr/bin/gq
kernel: 2.6.34.7-61.fc13.x86_64
package: gq-1.3.4-9.fc13
reason: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1291836453
uid: 500

How to reproduce
-----
1.Tryed to expand the root DN of our AD server
2.
3.
Comment 1 Adam Carbone 2010-12-08 19:28:56 UTC 
Created attachment 467556 [details]
File: backtrace
Comment 2 Terje Røsten 2011-01-17 15:12:03 UTC 

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