| Summary: | [abrt] openttd-1.2.0-0.1.RC4.fc17: __GI_raise: Process /usr/bin/openttd was killed by signal 6 (SIGABRT) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Simon Farnsworth <simon> | ||||||||||
| Component: | openttd | Assignee: | Felix Kaechele <felix> | ||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | anton, atorkhov, felix | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:6f7d375daa3502e1432aefa9efc9cf0cd49bd2f2 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-04-15 15:47:41 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Simon Farnsworth
2012-04-14 21:23:12 UTC
Created attachment 577482 [details]
File: backtrace
Created attachment 577483 [details]
File: maps
Did you have OpenTTD 0.5 or older installed at some point, or was you config directory created by a OpenTTD version older than 0.5? Could you just try to rename your ~/.openttd folder and have OpenTTD create a new one? Also upstream would be very interested in having the crash.log and crash.dmp that OpenTTD should have created in the ~/.openttd folder when it crashed. If you need any assistance with this I'm here to help :) I've played various versions of OpenTTD - 0.5 is plausible. Renaming .openttd to .openttd.crash caused it to crash. I can't find crash.dmp in .openttd: simon@lister:~$ find ~/.openttd.crash/ -name 'crash.*' /home/simon/.openttd.crash/crash.log simon@lister:~$ I will upload crash.log shortly. Created attachment 577506 [details]
crash.log from the crashed openttd
crash.log, as requested. Can't find crash.dmp - otherwise I'd upload that too.
Accidentally used my work Bugzilla account to add the crashdump, not my personal one - fixing up the CC list. Okay, so what we think happens here is that an error is found while loading the config file. The error you are seeing is given when loading of the config fails in a very early stage (i.e. before a language file is loaded). This is most likely due to an error in the [misc] section of the config file. Did I understand you correctly that this even occurs when you have OpenTTD completely regenerate the config file? Is there a chance that some files of an old OpenTTD may be still lingering around your filesystem? Upstream bug report is here: http://bugs.openttd.org/task/5154 I have been unclear - renaming .openttd to .openttd.crash permitted OpenTTD to start properly, at the expense of losing all my settings (obviously). Would a copy of openttd.cfg from the failing .openttd directory be of interest to either you or upstream? If so, I can upload it here. Yes a copy of the failing openttd.cfg would be great. Created attachment 577537 [details]
openttd.cfg that is suspected of crashing OpenTTD
Here's the openttd.cfg - I've got the entire configuration directory to one side (not interfering with my entertainment), so I can give you other files from it as desired.
Okay so thanks for pointing this bug out. Upstream will try to have OpenTTD show a helpful error message if the misc section of the config is broken. To fix your specific bug you can do this in your .openttd directory (the one that was failing): sed -i 's/TRANS_BUILDINGS|FULL_DETAIL|WAYPOINTS/FULL_DETAIL|WAYPOINTS|SHOW_COMPETITOR_SIGNS/' openttd.cfg This should fix the startup error but leave all your settings intact. (In reply to comment #12) > Okay so thanks for pointing this bug out. Upstream will try to have OpenTTD > show a helpful error message if the misc section of the config is broken. > Thank you for taking the time to handle this bug report and take it to upstream. > To fix your specific bug you can do this in your .openttd directory (the one > that was failing): > sed -i > 's/TRANS_BUILDINGS|FULL_DETAIL|WAYPOINTS/FULL_DETAIL|WAYPOINTS|SHOW_COMPETITOR_SIGNS/' > openttd.cfg > > This should fix the startup error but leave all your settings intact. I can confirm that this fixes the start error, and leaves my settings in place. Sure, no problem. Thank you for taking the time to filing this bug :) |