Version-Release number of selected component: sumwars-0.5.6-16.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/sumwars executable: /usr/bin/sumwars kernel: 3.13.5-202.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (0 frames)
Created attachment 874225 [details] File: backtrace
Created attachment 874226 [details] File: cgroup
Created attachment 874227 [details] File: core_backtrace
Created attachment 874228 [details] File: dso_list
Created attachment 874229 [details] File: environ
Created attachment 874230 [details] File: exploitable
Created attachment 874231 [details] File: limits
Created attachment 874232 [details] File: maps
Created attachment 874233 [details] File: open_fds
Created attachment 874234 [details] File: proc_pid_status
Created attachment 874235 [details] File: var_log_messages
SIGSEGV seems to occur upon closing after apparent lua incompatibility soon after arriving at joringsbridge (first movement made after arrival diverts to what should be a conversation between several characters, but all action freezes except ability to press <esc> to exit). It is at this exit that SIGSEGV seems to occur. I tried rebuilding strictly on lua 5.1 (using ccmake, adding /lua-5.1 to include path), after applying all but lua patch. Everything seems to work after that, but a segment-fault occurs upon every exit. I can try to grab the coredump to attach if needed (probably should be attached to a new/different bug report?)
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.
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.