Bug 662320

Summary: [abrt] glest-3.2.2-6.fc14: Process /usr/libexec/glest/glest was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: C.J.H. <cogre666>
Component: glestAssignee: Bruno Wolff III <bruno>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: alan.brault, bruno, fedora-bugzilla, raul.giucich
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:cbee3657544a77a8979a3dc8443b64283bc33720
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 17:36:29 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 C.J.H. 2010-12-11 15:23:51 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/glest/glest
comment: I was playing the game for most of the night (1920x1080 full screen) using "a "custom game". When I exited out of the custom game and selected scenario...and basically lost right away, after hitting escape I then selected join game....and Glest crashed.
component: glest
crash_function: Glest::Game::NetworkManager::init
executable: /usr/libexec/glest/glest
kernel: 2.6.35.9-64.fc14.x86_64
package: glest-3.2.2-6.fc14
rating: 4
reason: Process /usr/libexec/glest/glest was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1292079518
uid: 1000

How to reproduce
-----
1.play the game
2.exit out of a custom game
3.start a scenario
4.exit out of the scenario ('cause was losing)
5.selected "join game"
6.crash

Comment 1 C.J.H. 2010-12-11 15:23:52 UTC
Created attachment 468153 [details]
File: backtrace

Comment 2 Raúl Giucich 2011-04-05 14:56:00 UTC
Package: glest-3.2.2-6.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. n/a
2.
3.

Comment 3 Catalin BOIE 2011-04-24 15:54:55 UTC
Package: glest-3.2.2-6.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I do not really know.
2.
3.

Comment 4 Catalin BOIE 2011-04-24 16:02:40 UTC
Package: glest-3.2.2-6.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. After finishing a game, start again.
2.
3.

Comment 5 abrt-bot 2012-03-21 16:54:45 UTC
*** Bug 772819 has been marked as a duplicate of this bug. ***

Comment 6 Fedora End Of Life 2012-08-16 17:36:33 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping