|Summary:||[abrt] openttd-1.2.2-1.fc17: Process /usr/bin/openttd was killed by signal 6 (SIGABRT)|
|Product:||[Fedora] Fedora||Reporter:||Jan Teichmann <jan.teichmann>|
|Component:||openttd||Assignee:||Felix Kaechele <felix>|
|Status:||CLOSED WONTFIX||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||17||CC:||anton, atorkhov, felix|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-08-01 17:03:41 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jan Teichmann 2012-10-07 16:03:00 UTC
Version-Release number of selected component: openttd-1.2.2-1.fc17 Additional info: libreport version: 2.0.13 abrt_version: 2.0.12 backtrace_rating: 4 cmdline: openttd crash_function: pthread_cond_wait@@GLIBC_2.3.2 kernel: 3.5.4-1.fc17.x86_64 truncated backtrace: :Thread no. 2 (1 frames) : #0 pthread_cond_wait@@GLIBC_2.3.2 at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S
Comment 1 Jan Teichmann 2012-10-07 16:03:03 UTC
Created attachment 623021 [details] File: core_backtrace
Comment 9 Jan Teichmann 2012-10-07 16:03:20 UTC
Created attachment 623029 [details] File: var_log_messages
Comment 10 Felix Kaechele 2012-10-07 16:34:29 UTC
Hi there, thanks for your bug report. Can you reproduce this bug or did it happen at random? Did OpenTTD create the crash diagnostic files (crash.log, crash.png, crash.sav) in the ~/.openttd folder?
Comment 11 Jan Teichmann 2012-10-07 17:01:30 UTC
I consider OpenTTD as super stable and never had any crash before. It happened randomly by scrolling through the map and I'm not able to reproduce the crash. I attach the diagnostic files. Btw, thanks for such an addictive game! ;)
Comment 12 Jan Teichmann 2012-10-07 17:02:33 UTC
Created attachment 623049 [details] openttd crash log the crash log from ./openttd
Comment 15 Felix Kaechele 2013-02-13 22:45:19 UTC
Did you ever encount this issue again?
Comment 16 Jan Teichmann 2013-02-14 11:18:42 UTC
no I didn't.
Comment 17 Fedora End Of Life 2013-07-04 05:48:59 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 18 Fedora End Of Life 2013-08-01 17:03:47 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.