Bug 872801

Summary: [abrt] 0ad-0.0.11-3.fc17: sem_wait: Process /usr/bin/pyrogenesis was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Thibaud de Borggraef <thibaud.deborggraef>
Component: 0adAssignee: Paulo Andrade <paulo.cesar.pereira.de.andrade>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: bioinfornatics, paulo.cesar.pereira.de.andrade
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:304069badeb6a3ac6093336e82e39204eaec723b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:17:22 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: xsession_errors
none
File: dso_list
none
File: maps
none
File: build_ids
none
File: proc_pid_status
none
File: open_fds
none
File: var_log_messages
none
0ad-saveas.patch none

Description Thibaud de Borggraef 2012-11-03 10:23:22 UTC
Description of problem:
 The program crashed when trying to save an editor-map

Version-Release number of selected component:
0ad-0.0.11-3.fc17

Additional info:
libreport version: 2.0.16
abrt_version:   2.0.16
backtrace_rating: 4
cmdline:        /usr/bin/pyrogenesis
crash_function: sem_wait
kernel:         3.6.3-1.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 sem_wait at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_wait.S:86
: #1 MessagePasserImpl::Query at ../../../source/tools/atlas/GameInterface/MessagePasserImpl.cpp:169
: #2 Post at ../../../source/tools/atlas/AtlasUI/ScenarioEditor/ScenarioEditor.cpp:1022
: #3 ScenarioEditor::OnSaveAs at ../../../source/tools/atlas/AtlasUI/ScenarioEditor/ScenarioEditor.cpp:813
: #4 ProcessEventIfMatches at src/common/event.cpp:1239
: #5 wxEvtHandler::ProcessEventIfMatches at src/common/event.cpp:1214
: #6 wxEventHashTable::HandleEvent at src/common/event.cpp:906
: #7 ProcessEvent at src/common/event.cpp:1301
: #8 wxEvtHandler::ProcessEvent at src/common/event.cpp:1272
: #9 gtk_menu_clicked_callback at src/gtk/menu.cpp:653

Comment 1 Thibaud de Borggraef 2012-11-03 10:23:25 UTC
Created attachment 637446 [details]
File: core_backtrace

Comment 2 Thibaud de Borggraef 2012-11-03 10:23:27 UTC
Created attachment 637447 [details]
File: environ

Comment 3 Thibaud de Borggraef 2012-11-03 10:23:29 UTC
Created attachment 637448 [details]
File: backtrace

Comment 4 Thibaud de Borggraef 2012-11-03 10:23:31 UTC
Created attachment 637449 [details]
File: limits

Comment 5 Thibaud de Borggraef 2012-11-03 10:23:33 UTC
Created attachment 637450 [details]
File: cgroup

Comment 6 Thibaud de Borggraef 2012-11-03 10:23:35 UTC
Created attachment 637451 [details]
File: smolt_data

Comment 7 Thibaud de Borggraef 2012-11-03 10:23:37 UTC
Created attachment 637452 [details]
File: xsession_errors

Comment 8 Thibaud de Borggraef 2012-11-03 10:23:39 UTC
Created attachment 637453 [details]
File: dso_list

Comment 9 Thibaud de Borggraef 2012-11-03 10:23:41 UTC
Created attachment 637454 [details]
File: maps

Comment 10 Thibaud de Borggraef 2012-11-03 10:23:42 UTC
Created attachment 637455 [details]
File: build_ids

Comment 11 Thibaud de Borggraef 2012-11-03 10:23:44 UTC
Created attachment 637456 [details]
File: proc_pid_status

Comment 12 Thibaud de Borggraef 2012-11-03 10:23:46 UTC
Created attachment 637457 [details]
File: open_fds

Comment 13 Thibaud de Borggraef 2012-11-03 10:23:48 UTC
Created attachment 637458 [details]
File: var_log_messages

Comment 14 Paulo Andrade 2012-11-03 17:24:49 UTC
For a "quick fix" so that you can actually save and test your maps, I
suggest this procedure:

$ sudo mkdir /usr/share/0ad/public/maps
$ sudo chmod 7777 /usr/share/0ad/public/maps
$ 0ad -editor

In the editor, when saving, ignore path selection (the game will ignore
anyway), but save in the above path. Supposing you did choose the name as
"mymap", then you can test it running

$ 0ad -autostart=mymap

I will try to make a patch to make it at least not crash, and give a
reasonable error message, but should leave build pending for the next
update.

Comment 15 Paulo Andrade 2012-11-03 20:16:56 UTC
Created attachment 637645 [details]
0ad-saveas.patch

This unofficial (hackish) patch should be added to the next
alpha rpm package. It should help in making it easier to
create custom maps and testing them.

Comment 16 MERCIER Jonathan 2012-11-14 16:13:42 UTC
pcpa nice jobs but :
/usr/share/0ad/mods/public/maps/scenarios seem to be hardcoded
if it take scenario from ~/.local/usr/share/0ad.... what happen ?

Comment 17 Paulo Andrade 2012-11-14 20:13:14 UTC
(In reply to comment #16)
> pcpa nice jobs but :
> /usr/share/0ad/mods/public/maps/scenarios seem to be hardcoded
> if it take scenario from ~/.local/usr/share/0ad.... what happen ?

It fails :-)

My patch simply does not allow one to attempt that, instead of
fixing it to work...

I just did debug the issue, overview what it does and make a
simple patch to address the issue found by the bug report, and
suggest a way to do some experimental map making.

If one is going to put significant efforts in modding or custom
map making, I suggest doing it with upstream involved as much
as possible.

Comment 18 Fedora End Of Life 2013-07-04 02:23:51 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 19 Fedora End Of Life 2013-08-01 08:17:25 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.