Bug 537032 - [abrt] crash detected in lordsawar-0.1.6-2.fc12
Summary: [abrt] crash detected in lordsawar-0.1.6-2.fc12
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: lordsawar
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bruno Wolff III
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d2e7c63c4383c330233e7790fd6...
: 537030 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-12 09:36 UTC by Douglas Furlong
Modified: 2010-12-04 03:22 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-04 03:22:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.88 KB, text/plain)
2009-11-12 09:36 UTC, Douglas Furlong
no flags Details

Description Douglas Furlong 2009-11-12 09:36:29 UTC
abrt detected a crash.

Comment: I think this may be happening when I attempt to load a saved game.
Attached file: backtrace
cmdline: lordsawar
component: lordsawar
executable: /usr/bin/lordsawar
kernel: 2.6.31.5-127.fc12.i686.PAE
package: lordsawar-0.1.6-2.fc12
rating: 3
reason: Process was terminated by signal 11

Comment 1 Douglas Furlong 2009-11-12 09:36:32 UTC
Created attachment 369163 [details]
File: backtrace

Comment 2 Ian Weller 2009-11-12 13:31:32 UTC
*** Bug 537030 has been marked as a duplicate of this bug. ***

Comment 3 Ben Asselstine 2009-11-12 17:24:16 UTC
Hi.  I'm the upstream author of Lordsawar.

From the backtrace it looks like a crash related to freeing a fortified stack graphic.  A fortified graphic is the tent/tower that the stack appears to be inside of, after you put the stack into "defend" mode.

Can you please try duplicating this bug by following these steps:
1. create a new game consisting of one human player and the remainder as easy AI players.
2. put a single stack into defend mode
3. end the turn
4. when it's your turn again, and you can see the stack in the fortified state, close the game in a normal fashion.
5.  when you get back to the main menu, click quit.

The graphics cache will be deleted at some point, and it should cause the same crash.

Ian, if Douglas can't do this,  can you try it please?

cheers,

Ben

Comment 4 Bug Zapper 2010-11-04 06:30:22 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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

Comment 5 Fedora Admin XMLRPC Client 2010-11-13 20:38:03 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Bug Zapper 2010-12-04 03:22:25 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.