Bug 1156228

Summary: [abrt] warzone2100: fprintf(): warzone2100 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikhail Yarashevich <aloner>
Component: warzone2100Assignee: Karol Trzcionka <karlikt>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jsynacek, karlikt
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/3e16a421e03ac5e908c8df2d66115c44f87d25ed
Whiteboard: abrt_hash:43197dd29e3275c1c9aa8be0ab1a2c07506a85df
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 23:01:28 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Mikhail Yarashevich 2014-10-23 21:54:35 UTC 
Version-Release number of selected component:
warzone2100-3.1.1-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        warzone2100
crash_function: fprintf
executable:     /usr/bin/warzone2100
kernel:         3.16.6-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 fprintf at /usr/include/bits/stdio2.h:97
 #1 pushbuf_dump at pushbuf.c:303
 #2 pushbuf_submit at pushbuf.c:361
 #3 pushbuf_flush at pushbuf.c:402
 #4 nouveau_pushbuf_kick at pushbuf.c:774
 #5 PUSH_KICK at ./nouveau_winsys.h:56
 #6 nv50_flush at nv50/nv50_context.c:44
 #7 st_context_flush at state_tracker/st_manager.c:464
 #8 dri_flush at dri_drawable.c:526
 #9 dri2SwapBuffers at dri2_glx.c:853
Comment 1 Mikhail Yarashevich 2014-10-23 21:54:39 UTC 
Created attachment 950090 [details]
File: backtrace
Comment 2 Mikhail Yarashevich 2014-10-23 21:54:40 UTC 
Created attachment 950091 [details]
File: cgroup
Comment 3 Mikhail Yarashevich 2014-10-23 21:54:42 UTC 
Created attachment 950092 [details]
File: core_backtrace
Comment 4 Mikhail Yarashevich 2014-10-23 21:54:43 UTC 
Created attachment 950093 [details]
File: dso_list
Comment 5 Mikhail Yarashevich 2014-10-23 21:54:44 UTC 
Created attachment 950094 [details]
File: environ
Comment 6 Mikhail Yarashevich 2014-10-23 21:54:45 UTC 
Created attachment 950095 [details]
File: limits
Comment 7 Mikhail Yarashevich 2014-10-23 21:54:48 UTC 
Created attachment 950096 [details]
File: maps
Comment 8 Mikhail Yarashevich 2014-10-23 21:54:49 UTC 
Created attachment 950097 [details]
File: open_fds
Comment 9 Mikhail Yarashevich 2014-10-23 21:54:51 UTC 
Created attachment 950098 [details]
File: proc_pid_status
Comment 10 Mikhail Yarashevich 2014-10-23 21:54:52 UTC 
Created attachment 950099 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2015-05-29 13:09:02 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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 12 Fedora End Of Life 2015-06-29 23:01:28 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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