Bug 592840 - [abrt] crash in gq-1.3.4-8.fc12: server_model_removed_server: Process /usr/bin/gq was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gq-1.3.4-8.fc12: server_model_removed_server: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 520342
Alias: None
Product: Fedora
Classification: Fedora
Component: gq
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:41972dae3ef9749388f4c069d4e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-17 07:08 UTC by Theophanis Kontogiannis
Modified: 2010-08-30 19:02 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-30 19:02:25 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (47.50 KB, text/plain)
2010-05-17 07:10 UTC, Theophanis Kontogiannis 		no flags Details
View All

Description Theophanis Kontogiannis 2010-05-17 07:08:59 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gq
component: gq
crash_function: server_model_removed_server
executable: /usr/bin/gq
global_uuid: 41972dae3ef9749388f4c069d4e2ebeefcd13c23
kernel: 2.6.32.11-99.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)

How to reproduce
-----
1. added one more server
2.
3.
Comment 1 Theophanis Kontogiannis 2010-05-17 07:10:44 UTC 
Created attachment 414464 [details]
File: backtrace
Comment 2 Theophanis Kontogiannis 2010-05-20 19:39:35 UTC 
Package: gq-1.3.4-8.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


How to reproduce
-----
1. added one more server
2.
3.
Comment 3 Terje Røsten 2010-08-30 19:02:25 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.