Bug 623159

Summary: [abrt] crash in gq-1.3.4-8.fc12: strcmp: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: bethebeast <bethebeast>
Component: gqAssignee: Terje Røsten <terjeros>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: terjeros
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:0c249660a014c611826317bf5e8714fa8137746a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-30 15:13:25 EDT 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 bethebeast 2010-08-11 09:30:42 EDT
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gq
comment: just try to connect to ldap server : right click and select "refresh"
component: gq
crash_function: strcmp
executable: /usr/bin/gq
global_uuid: 0c249660a014c611826317bf5e8714fa8137746a
package: gq-1.3.4-8.fc12
rating: 3
reason: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. open gq
2. add new server
3. refresh the left panel
Comment 1 bethebeast 2010-08-11 09:30:45 EDT
Created attachment 438187 [details]
File: backtrace
Comment 2 Terje Røsten 2010-08-30 15:13:25 EDT
There are a number of problematic issues with gq_ a lot of crashes and a dead
upstream. Seems like the best way forward is to find a good replacement.

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