Bug 912869

Summary: [abrt] warzone2100-3.1.0-1.fc17: droidTemplateShutDown: Process /usr/bin/warzone2100 was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: jk <jim>
Component: warzone2100Assignee: Karol Trzcionka <karlikt>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jsynacek, karlikt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:66b2aaf2eec87f19e836c5552c34c07faa31ef4f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 02:06:12 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: var_log_messages
none
File: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: build_ids
none
File: proc_pid_status
none
File: open_fds none

Description jk 2013-02-19 21:38:01 UTC 
Description of problem:
don't know.  message popped up when i rebooted.

Version-Release number of selected component:
warzone2100-3.1.0-1.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        warzone2100
crash_function: droidTemplateShutDown
kernel:         3.7.3-101.fc17.x86_64

truncated backtrace:
:Thread no. 1 (5 frames)
: #5 droidTemplateShutDown at template.cpp:448
: #6 resReleaseAllData at frameresource.cpp:751
: #7 resReleaseAll at frameresource.cpp:722
: #8 systemShutdown at init.cpp:575
: #9 realmain at main.cpp:1334
Comment 1 jk 2013-02-19 21:38:04 UTC 
Created attachment 699664 [details]
File: var_log_messages
Comment 2 jk 2013-02-19 21:38:07 UTC 
Created attachment 699665 [details]
File: core_backtrace
Comment 3 jk 2013-02-19 21:38:08 UTC 
Created attachment 699666 [details]
File: environ
Comment 4 jk 2013-02-19 21:38:11 UTC 
Created attachment 699667 [details]
File: backtrace
Comment 5 jk 2013-02-19 21:38:12 UTC 
Created attachment 699668 [details]
File: limits
Comment 6 jk 2013-02-19 21:38:14 UTC 
Created attachment 699669 [details]
File: cgroup
Comment 7 jk 2013-02-19 21:38:16 UTC 
Created attachment 699670 [details]
File: smolt_data
Comment 8 jk 2013-02-19 21:38:19 UTC 
Created attachment 699671 [details]
File: executable
Comment 9 jk 2013-02-19 21:38:21 UTC 
Created attachment 699672 [details]
File: maps
Comment 10 jk 2013-02-19 21:38:23 UTC 
Created attachment 699673 [details]
File: dso_list
Comment 11 jk 2013-02-19 21:38:25 UTC 
Created attachment 699674 [details]
File: build_ids
Comment 12 jk 2013-02-19 21:38:27 UTC 
Created attachment 699675 [details]
File: proc_pid_status
Comment 13 jk 2013-02-19 21:38:28 UTC 
Created attachment 699676 [details]
File: open_fds
Comment 14 Fedora End Of Life 2013-07-03 23:25:26 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.
Comment 15 Fedora End Of Life 2013-08-01 02:06:16 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.