Bug 628389

Summary: [abrt] gq-1.3.4-8.fc12: server_model_removed_server: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: svk0 <svk0>
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: x86_64   
OS: Linux   
Whiteboard: abrt_hash:b83f7bdbda18f3592dbe1d17df67d6c8bde541d3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-30 15:14:44 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Attachments:
Description Flags
File: backtrace none

Description svk0 2010-08-29 17:14:56 EDT
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gq
comment: simple connect over vpn and i get crash client
component: gq
crash_function: server_model_removed_server
executable: /usr/bin/gq
kernel: 2.6.32.19-163.fc12.x86_64
package: gq-1.3.4-8.fc12
rating: 4
reason: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1283116174
uid: 500

How to reproduce
-----
1. connect to network over vpn
2. start client
3. configure
4. connect and crash client
Comment 1 svk0 2010-08-29 17:15:00 EDT
Created an attachment (id=441837)
File: backtrace
Comment 2 Terje Røsten 2010-08-30 15:14:44 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 ***